From aecf49d6c897c0dbdc34d99728b93c25c1f27305 Mon Sep 17 00:00:00 2001 From: "Martin Trigaux (mat)" Date: Thu, 18 Jan 2024 11:23:43 +0000 Subject: [PATCH] [I18N] *: export 16.0 translations closes odoo/documentation#7452 X-original-commit: 3917094efde056c9318f6758d1fbf1cfaf76d7f6 Signed-off-by: Martin Trigaux (mat) --- locale/sources/administration.pot | 328 +- locale/sources/developer.pot | 595 ++- locale/sources/finance.pot | 4412 +++++++++++++------- locale/sources/general.pot | 2 +- locale/sources/hr.pot | 5538 ++++++++++++++++++++------ locale/sources/inventory_and_mrp.pot | 2027 +++++++--- locale/sources/legal.pot | 539 ++- locale/sources/marketing.pot | 2 +- locale/sources/productivity.pot | 42 +- locale/sources/sales.pot | 2776 ++++++++++--- locale/sources/services.pot | 4 +- locale/sources/websites.pot | 410 +- 12 files changed, 12399 insertions(+), 4276 deletions(-) diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 41d74ad94c..a9d0fcf531 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -890,6 +890,82 @@ msgstr "" msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." msgstr "" +#: ../../content/administration/install/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:11 +msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:25 +msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:41 +msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:54 +msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:56 +msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:58 +msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:60 +msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:62 +msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." +msgstr "" + #: ../../content/administration/install/online.rst:3 msgid "Online" msgstr "" @@ -910,8 +986,8 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:166 #: ../../content/administration/maintain/domain_names.rst:236 #: ../../content/administration/maintain/supported_versions.rst:29 -#: ../../content/administration/upgrade.rst:92 -#: ../../content/administration/upgrade.rst:309 +#: ../../content/administration/upgrade.rst:90 +#: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" msgstr "" @@ -2005,8 +2081,8 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:250 #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/odoo_sh.rst:5 -#: ../../content/administration/upgrade.rst:122 -#: ../../content/administration/upgrade.rst:320 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 msgid "Odoo.sh" msgstr "" @@ -6031,58 +6107,58 @@ msgid "Migrating from another ERP to Odoo" msgstr "" #: ../../content/administration/upgrade.rst:42 -msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**." +msgid "If your database contains custom modules, it cannot be upgraded until a version of your custom modules is available for the target version of Odoo. For customers maintaining their own custom modules, we recommend to parallelize the process by :ref:`requesting an upgraded database ` while also :doc:`upgrading the source code of your custom modules `." msgstr "" -#: ../../content/administration/upgrade.rst:49 +#: ../../content/administration/upgrade.rst:50 msgid "Upgrading in a nutshell" msgstr "" -#: ../../content/administration/upgrade.rst:51 +#: ../../content/administration/upgrade.rst:52 msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database `)." msgstr "" -#: ../../content/administration/upgrade.rst:54 -msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." +#: ../../content/administration/upgrade.rst:55 +msgid "If applicable, upgrade the source code of your custom module to be compatible with the new version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`)." msgstr "" -#: ../../content/administration/upgrade.rst:57 -msgid "Report any issue encountered during the testing to Odoo via the `support page `__." +#: ../../content/administration/upgrade.rst:58 +msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." msgstr "" -#: ../../content/administration/upgrade.rst:60 -msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo." +#: ../../content/administration/upgrade.rst:61 +msgid "Report any issue encountered during the testing to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:63 +#: ../../content/administration/upgrade.rst:64 msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database." msgstr "" -#: ../../content/administration/upgrade.rst:66 +#: ../../content/administration/upgrade.rst:67 msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database `)." msgstr "" -#: ../../content/administration/upgrade.rst:69 +#: ../../content/administration/upgrade.rst:70 msgid "Report any issue encountered during the upgrade to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:78 +#: ../../content/administration/upgrade.rst:76 msgid "Obtaining an upgraded test database" msgstr "" -#: ../../content/administration/upgrade.rst:80 +#: ../../content/administration/upgrade.rst:78 msgid "The `Upgrade page `_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager `_, or your `Odoo.sh project `_." msgstr "" -#: ../../content/administration/upgrade.rst:86 +#: ../../content/administration/upgrade.rst:84 msgid "The Upgrade platform follows the same `Privacy Policy `_ as the other Odoo.com services. Visit the `General Data Protection Regulation page `_ to learn more about how Odoo handles your data and privacy." msgstr "" -#: ../../content/administration/upgrade.rst:94 +#: ../../content/administration/upgrade.rst:92 msgid "Odoo Online databases can be manually upgraded via the `database manager `_." msgstr "" -#: ../../content/administration/upgrade.rst:97 +#: ../../content/administration/upgrade.rst:95 msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded." msgstr "" @@ -6090,19 +6166,19 @@ msgstr "" msgid "The database manager with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade.rst:104 +#: ../../content/administration/upgrade.rst:102 msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:" msgstr "" -#: ../../content/administration/upgrade.rst:106 +#: ../../content/administration/upgrade.rst:104 msgid "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" -#: ../../content/administration/upgrade.rst:107 +#: ../../content/administration/upgrade.rst:105 msgid "The **email** address that should receive the link to the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:108 +#: ../../content/administration/upgrade.rst:106 msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request" msgstr "" @@ -6110,7 +6186,7 @@ msgstr "" msgid "The \"Upgrade your database\" popup." msgstr "" -#: ../../content/administration/upgrade.rst:114 +#: ../../content/administration/upgrade.rst:112 msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name." msgstr "" @@ -6118,7 +6194,7 @@ msgstr "" msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" -#: ../../content/administration/upgrade.rst:124 +#: ../../content/administration/upgrade.rst:122 msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process." msgstr "" @@ -6126,272 +6202,280 @@ msgstr "" msgid "Odoo.sh project and tabs" msgstr "" -#: ../../content/administration/upgrade.rst:129 +#: ../../content/administration/upgrade.rst:127 msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform `_." msgstr "" -#: ../../content/administration/upgrade.rst:132 +#: ../../content/administration/upgrade.rst:130 msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`." msgstr "" -#: ../../content/administration/upgrade.rst:140 +#: ../../content/administration/upgrade.rst:138 msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited." msgstr "" -#: ../../content/administration/upgrade.rst:152 -#: ../../content/administration/upgrade.rst:344 +#: ../../content/administration/upgrade.rst:143 +msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." +msgstr "" + +#: ../../content/administration/upgrade.rst:145 +#: ../../content/administration/upgrade.rst:341 msgid "On-premise" msgstr "" -#: ../../content/administration/upgrade.rst:154 +#: ../../content/administration/upgrade.rst:147 msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" -#: ../../content/administration/upgrade.rst:161 +#: ../../content/administration/upgrade.rst:154 msgid "The following command can be used to display the general help and the main commands:" msgstr "" -#: ../../content/administration/upgrade.rst:167 +#: ../../content/administration/upgrade.rst:160 msgid "An upgraded test database can also be requested via the `Upgrade page `_." msgstr "" -#: ../../content/administration/upgrade.rst:171 +#: ../../content/administration/upgrade.rst:164 +msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." +msgstr "" + +#: ../../content/administration/upgrade.rst:169 msgid "For security reasons, only the person who submitted the upgrade request can download it." msgstr "" -#: ../../content/administration/upgrade.rst:172 +#: ../../content/administration/upgrade.rst:170 msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." msgstr "" -#: ../../content/administration/upgrade.rst:174 +#: ../../content/administration/upgrade.rst:172 msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version." msgstr "" -#: ../../content/administration/upgrade.rst:177 +#: ../../content/administration/upgrade.rst:175 msgid "The upgraded database contains:" msgstr "" -#: ../../content/administration/upgrade.rst:179 +#: ../../content/administration/upgrade.rst:177 msgid "A `dump.sql` file containing the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:180 +#: ../../content/administration/upgrade.rst:178 msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." msgstr "" -#: ../../content/administration/upgrade.rst:187 +#: ../../content/administration/upgrade.rst:185 msgid "You can request multiple test databases if you wish to test an upgrade more than once." msgstr "" -#: ../../content/administration/upgrade.rst:192 +#: ../../content/administration/upgrade.rst:190 msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version." msgstr "" -#: ../../content/administration/upgrade.rst:200 +#: ../../content/administration/upgrade.rst:198 msgid "Testing the new version of the database" msgstr "" -#: ../../content/administration/upgrade.rst:202 +#: ../../content/administration/upgrade.rst:200 msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live." msgstr "" -#: ../../content/administration/upgrade.rst:207 +#: ../../content/administration/upgrade.rst:205 msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:" msgstr "" -#: ../../content/administration/upgrade.rst:210 +#: ../../content/administration/upgrade.rst:208 msgid "Scheduled actions are disabled." msgstr "" -#: ../../content/administration/upgrade.rst:211 +#: ../../content/administration/upgrade.rst:209 msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one." msgstr "" -#: ../../content/administration/upgrade.rst:212 +#: ../../content/administration/upgrade.rst:210 msgid "Payment providers and delivery carriers are reset to the test environment." msgstr "" -#: ../../content/administration/upgrade.rst:213 +#: ../../content/administration/upgrade.rst:211 msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials." msgstr "" -#: ../../content/administration/upgrade.rst:216 +#: ../../content/administration/upgrade.rst:214 msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version." msgstr "" -#: ../../content/administration/upgrade.rst:219 +#: ../../content/administration/upgrade.rst:217 msgid "Basic test checklist" msgstr "" -#: ../../content/administration/upgrade.rst:221 +#: ../../content/administration/upgrade.rst:219 msgid "Are there views that are deactivated in your test database but active in your production database?" msgstr "" -#: ../../content/administration/upgrade.rst:223 +#: ../../content/administration/upgrade.rst:221 msgid "Are your usual views still displayed correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:224 +#: ../../content/administration/upgrade.rst:222 msgid "Are your reports (invoice, sales order, etc.) correctly generated?" msgstr "" -#: ../../content/administration/upgrade.rst:225 +#: ../../content/administration/upgrade.rst:223 msgid "Are your website pages working correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:226 +#: ../../content/administration/upgrade.rst:224 msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:228 +#: ../../content/administration/upgrade.rst:226 msgid "Are there any issues with your mail templates?" msgstr "" -#: ../../content/administration/upgrade.rst:229 +#: ../../content/administration/upgrade.rst:227 msgid "Are there any issues with saved translations?" msgstr "" -#: ../../content/administration/upgrade.rst:230 +#: ../../content/administration/upgrade.rst:228 msgid "Are your search filters still present?" msgstr "" -#: ../../content/administration/upgrade.rst:231 +#: ../../content/administration/upgrade.rst:229 msgid "Can you export your data?" msgstr "" -#: ../../content/administration/upgrade.rst:235 +#: ../../content/administration/upgrade.rst:233 msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)." msgstr "" -#: ../../content/administration/upgrade.rst:238 +#: ../../content/administration/upgrade.rst:236 msgid "Buying this product (Purchase app)." msgstr "" -#: ../../content/administration/upgrade.rst:239 +#: ../../content/administration/upgrade.rst:237 msgid "Confirming the reception of this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:240 +#: ../../content/administration/upgrade.rst:238 msgid "Checking if the route to receive this product is the same in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:242 +#: ../../content/administration/upgrade.rst:240 msgid "Selling this product (Sales app) to a random customer." msgstr "" -#: ../../content/administration/upgrade.rst:243 +#: ../../content/administration/upgrade.rst:241 msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data." msgstr "" -#: ../../content/administration/upgrade.rst:245 +#: ../../content/administration/upgrade.rst:243 msgid "Shipping this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:246 +#: ../../content/administration/upgrade.rst:244 msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:248 +#: ../../content/administration/upgrade.rst:246 msgid "Validating a customer invoice (Invoicing or Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:249 +#: ../../content/administration/upgrade.rst:247 msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database." msgstr "" -#: ../../content/administration/upgrade.rst:251 +#: ../../content/administration/upgrade.rst:249 msgid "Checking your reports' results (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:252 +#: ../../content/administration/upgrade.rst:250 msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:253 +#: ../../content/administration/upgrade.rst:251 msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database." msgstr "" -#: ../../content/administration/upgrade.rst:256 +#: ../../content/administration/upgrade.rst:254 msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:258 +#: ../../content/administration/upgrade.rst:256 msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database." msgstr "" -#: ../../content/administration/upgrade.rst:263 +#: ../../content/administration/upgrade.rst:261 msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:269 +#: ../../content/administration/upgrade.rst:267 msgid "Do not forget to test:" msgstr "" -#: ../../content/administration/upgrade.rst:271 +#: ../../content/administration/upgrade.rst:269 msgid "Integrations with external software (EDI, APIs, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:272 +#: ../../content/administration/upgrade.rst:270 msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:274 +#: ../../content/administration/upgrade.rst:272 msgid "Data exports" msgstr "" -#: ../../content/administration/upgrade.rst:275 +#: ../../content/administration/upgrade.rst:273 msgid "Automated actions" msgstr "" -#: ../../content/administration/upgrade.rst:276 +#: ../../content/administration/upgrade.rst:274 msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views" msgstr "" -#: ../../content/administration/upgrade.rst:282 +#: ../../content/administration/upgrade.rst:280 msgid "Upgrading the production database" msgstr "" -#: ../../content/administration/upgrade.rst:284 +#: ../../content/administration/upgrade.rst:282 msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:289 +#: ../../content/administration/upgrade.rst:287 msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal." msgstr "" -#: ../../content/administration/upgrade.rst:292 -msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. Fully rehearsing the upgrade process the day before upgrading the production database is also recommended." +#: ../../content/administration/upgrade.rst:290 +msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the day before upgrading the production database is also recommended.**" msgstr "" -#: ../../content/administration/upgrade.rst:298 +#: ../../content/administration/upgrade.rst:296 msgid "Going into production without first testing may lead to:" msgstr "" -#: ../../content/administration/upgrade.rst:300 +#: ../../content/administration/upgrade.rst:298 msgid "Users failing to adjust to the changes and new features" msgstr "" -#: ../../content/administration/upgrade.rst:301 +#: ../../content/administration/upgrade.rst:299 msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" msgstr "" -#: ../../content/administration/upgrade.rst:302 +#: ../../content/administration/upgrade.rst:300 msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" msgstr "" -#: ../../content/administration/upgrade.rst:304 +#: ../../content/administration/upgrade.rst:302 msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." msgstr "" -#: ../../content/administration/upgrade.rst:311 +#: ../../content/administration/upgrade.rst:309 msgid "The process is similar to :ref:`obtaining an upgraded test database `, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`." msgstr "" -#: ../../content/administration/upgrade.rst:316 +#: ../../content/administration/upgrade.rst:314 msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version." msgstr "" -#: ../../content/administration/upgrade.rst:322 +#: ../../content/administration/upgrade.rst:320 msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." msgstr "" @@ -6399,98 +6483,98 @@ msgstr "" msgid "View from the upgrade tab" msgstr "" -#: ../../content/administration/upgrade.rst:328 +#: ../../content/administration/upgrade.rst:326 msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately." msgstr "" -#: ../../content/administration/upgrade.rst:334 +#: ../../content/administration/upgrade.rst:332 msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created." msgstr "" -#: ../../content/administration/upgrade.rst:338 -msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production." +#: ../../content/administration/upgrade.rst:336 +msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`." msgstr "" -#: ../../content/administration/upgrade.rst:346 +#: ../../content/administration/upgrade.rst:343 msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:" msgstr "" -#: ../../content/administration/upgrade.rst:353 +#: ../../content/administration/upgrade.rst:350 msgid "An upgraded production database can also be requested via the `Upgrade page `_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process." msgstr "" -#: ../../content/administration/upgrade.rst:360 +#: ../../content/administration/upgrade.rst:357 msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." msgstr "" -#: ../../content/administration/upgrade.rst:364 +#: ../../content/administration/upgrade.rst:361 msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to the upgrade in production." msgstr "" -#: ../../content/administration/upgrade.rst:372 +#: ../../content/administration/upgrade.rst:369 msgid "Service-level agreement (SLA)" msgstr "" -#: ../../content/administration/upgrade.rst:374 +#: ../../content/administration/upgrade.rst:371 msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." msgstr "" -#: ../../content/administration/upgrade.rst:377 +#: ../../content/administration/upgrade.rst:374 msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." msgstr "" -#: ../../content/administration/upgrade.rst:382 +#: ../../content/administration/upgrade.rst:379 msgid "Upgrade services covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:384 +#: ../../content/administration/upgrade.rst:381 msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" msgstr "" -#: ../../content/administration/upgrade.rst:387 +#: ../../content/administration/upgrade.rst:384 msgid "the upgrade of all **standard applications**;" msgstr "" -#: ../../content/administration/upgrade.rst:388 +#: ../../content/administration/upgrade.rst:385 msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" msgstr "" -#: ../../content/administration/upgrade.rst:390 +#: ../../content/administration/upgrade.rst:387 msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." msgstr "" -#: ../../content/administration/upgrade.rst:393 +#: ../../content/administration/upgrade.rst:390 msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:397 +#: ../../content/administration/upgrade.rst:394 msgid "Upgrade services not covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:399 +#: ../../content/administration/upgrade.rst:396 msgid "The following upgrade-related services are **not** included:" msgstr "" -#: ../../content/administration/upgrade.rst:401 +#: ../../content/administration/upgrade.rst:398 msgid "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" -#: ../../content/administration/upgrade.rst:402 +#: ../../content/administration/upgrade.rst:399 msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" msgstr "" -#: ../../content/administration/upgrade.rst:403 +#: ../../content/administration/upgrade.rst:400 msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" msgstr "" -#: ../../content/administration/upgrade.rst:406 +#: ../../content/administration/upgrade.rst:403 msgid "**training** on using the upgraded version's features and workflows." msgstr "" -#: ../../content/administration/upgrade.rst:409 +#: ../../content/administration/upgrade.rst:406 msgid ":doc:`Odoo.sh documentation `" msgstr "" -#: ../../content/administration/upgrade.rst:410 +#: ../../content/administration/upgrade.rst:407 msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index 48f22e1720..c5a44c49dc 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -956,6 +956,7 @@ msgid "When the field `company_id` is made required on a model, a good practice msgstr "" #: ../../content/developer/howtos/company.rst:168 +#: ../../content/developer/howtos/upgrade_custom_db.rst:132 #: ../../content/developer/howtos/website_themes/setup.rst:75 #: ../../content/developer/howtos/website_themes/theming.rst:496 #: ../../content/developer/reference/frontend/javascript_reference.rst:1154 @@ -1599,6 +1600,7 @@ msgstr "" #: ../../content/developer/howtos/scss_tips.rst:85 #: ../../content/developer/howtos/scss_tips.rst:86 +#: ../../content/developer/howtos/upgrade_custom_db.rst:114 #: ../../content/developer/howtos/website_themes/shapes.rst:139 msgid "..." msgstr "" @@ -1999,6 +2001,351 @@ msgstr "" msgid "**Do** in the case where the translation lookup is done when the JS file is *read*, use `_lt` instead of `_t` to translate the term when it is *used*::" msgstr "" +#: ../../content/developer/howtos/upgrade_custom_db.rst:3 +msgid "Upgrade a customized database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:5 +msgid "Upgrading to a new version of Odoo can be challenging, especially if the database you work on contains custom modules. This page intent is to explain the technical process of upgrading a database with customized modules. Refer to :doc:`Upgrade documentation ` for guidance on how to upgrade a database without customized modules." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:10 +msgid "We consider a custom module, any module that extends the standard code of Odoo and that was not built with the Studio app. Before upgrading such a module, or before requesting its upgrade, have a look at the :ref:`upgrade/sla` to make sure who's responsible for it." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:14 +msgid "While working on what we refer to as the **custom upgrade** of your database, keep in mind the goals of an upgrade:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:17 +msgid "Stay supported" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:18 +msgid "Get the latest features" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:19 +msgid "Enjoy the performance improvement" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:20 +msgid "Reduce the technical debt" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:21 +msgid "Benefit from security improvements" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:23 +msgid "With every new version of Odoo, changes are introduced. These changes can impact modules on which customization have been developed. This is the reason why upgrading a database that contains custom modules requires additional steps in order to upgrade the source code." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:27 +msgid "These are the steps to follow to upgrade customized databases:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:29 +msgid ":ref:`Stop the devolopments and challenge them `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:30 +msgid ":ref:`Request an upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:31 +msgid ":ref:`Make your module installable on an empty database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:32 +msgid ":ref:`Make your module installable on the upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:33 +msgid ":ref:`Test extensively and do a rehearsal `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:34 +msgid ":ref:`Upgrade the production database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:40 +msgid "Step 1: Stop the developments" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:42 +msgid "Starting an upgrade requires commitment and development resources. If developments keep being made at the same time, those features will need to be re-upgraded and tested every time you change them. This is why we recommend a complete freeze of the codebase when starting the upgrade process. Needless to say, bug fixing is exempt from this recommendation." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:47 +msgid "Once you have stopped development, it is a good practice to assess the developments made and compare them with the features introduced between your current version and the version you are targeting. Challenge the developments as much as possible and find functional workarounds. Removing redundancy between your developments and the standard version of Odoo will lead to an eased upgrade process and reduce technical debt." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:54 +msgid "You can find information on the changes between versions in the `Release Notes `_." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:61 +msgid "Step 2: Request an upgraded database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:63 +msgid "Once the developments have stopped for the custom modules and the implemented features have been challenged to remove redundancy and unnecessary code, the next step is to request an upgraded test database. To do so, follow the steps mentioned in :ref:`upgrade/request-test-database`, depending on the hosting type of your database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:68 +msgid "The purpose of this stage is not to start working with the custom modules in the upgraded database, but to make sure the standard upgrade process works seamlessly, and the test database is delivered properly. If that's not the case, and the upgrade request fails, request the assistance of Odoo via the `support page `_ by selecting the option related to testing the upgrade." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:78 +msgid "Step 3: Empty database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:80 +msgid "Before working on an upgraded test database, we recommend to make the custom developments work on an empty database in the targeted version of your upgrade. This ensures that the customization is compatible with the new version of Odoo, allows to analyze how it behaves and interacts with the new features, and guarantees that they will not cause any issues when upgrading the database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:85 +msgid "Making the custom modules work in an empty database also helps avoid changes and wrong configurations that might be present in the production database (like studio customization, customized website pages, email templates or translations). They are not intrinsically related to the custom modules and that can raise unwanted issues in this stage of the upgraded process." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:90 +msgid "To make custom modules work on an empty database we advise to follow these steps:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:92 +msgid ":ref:`upgrade_custom/empty_database/modules_installable`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:93 +msgid ":ref:`upgrade_custom/empty_database/test_fixes`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:94 +msgid ":ref:`upgrade_custom/empty_database/clean_code`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:95 +msgid ":ref:`Make standard tests run successfully `" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:100 +msgid "Make custom modules installable" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:102 +msgid "The first step is to make the custom modules installable in the new Odoo version. This means, starting by ensuring there are no tracebacks or warnings during their installation. For this, install the custom modules, one by one, in an empty database of the new Odoo version and fix the tracebacks and warnings that arise from that." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:107 +msgid "This process will help detect issues during the installation of the modules. For example:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:109 +msgid "Invalid module dependencies." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:110 +msgid "Syntax change: assets declaration, OWL updates, attrs." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:111 +msgid "References to standard fields, models, views not existing anymore or renamed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:112 +msgid "Xpath that moved or were removed from views." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:113 +msgid "Methods renamed or removed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:119 +msgid "Test and fixes" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:121 +msgid "Once there are no more tracebacks when installing the modules, the next step is to test them. Even if the custom modules are installable on an empty database, this does not guarantee there are no errors during their execution. Because of this, we encourage to test thoroughly all the customization to make sure everything is working as expected." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:126 +msgid "This process will help detect further issues that are not identified during the module installation and can only be detected in runtime. For example, deprecated calls to standard python or OWL functions, non-existing references to standard fields, etc." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:130 +msgid "We recommend to test all the customization, especially the following elements:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:133 +msgid "Email templates" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:134 +msgid "Reports" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:135 +msgid "Server actions and automated actions" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:136 +msgid "Changes in the standard workflows" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:137 +#: ../../content/developer/tutorials/backend.rst:716 +msgid "Computed fields" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:139 +msgid "We also encourage to write automated tests to save time during the testing iterations, increase the test coverage, and ensure that the changes and fixes introduced do not break the existing flows. If there are tests already implemented in the customization, make sure they are upgraded to the new Odoo version and run successfully, fixing issues that might be present." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:147 +msgid "Clean the code" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:149 +msgid "At this stage of the upgrade process, we also suggest to clean the code as much as possible. This includes:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:152 +msgid "Remove redundant and unnecessary code." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:153 +msgid "Remove features that are now part of Odoo standard, as described in :ref:`upgrade_custom/stop_developments`." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:155 +msgid "Clean commented code if it is not needed anymore." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:156 +msgid "Refactor the code (functions, fields, views, reports, etc.) if needed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:161 +msgid "Standard tests" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:163 +msgid "Once the previous steps are completed, we advise to make sure all standard tests associated to the dependencies of the custom module pass. Standard tests ensure the validation of the code logic and prevent data corruption. They will help you identify bugs or unwanted behavior before you work on your database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:168 +msgid "In case there are standard test failing, we suggest to analyze the reason for their failure:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:170 +msgid "The customization changes the standard workflow: Adapt the standard test to your workflow." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:171 +msgid "The customization did not take into account a special flow: Adapt your customization to ensure it works for all the standard workflows." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:178 +msgid "Step 4: Upgraded database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:180 +msgid "Once the custom modules are installable and working properly in an empty database, it is time to make them work on an :ref:`upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:183 +msgid "To make sure the custom code is working flawlessly in the new version, follow these steps:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:185 +msgid ":ref:`upgrade_custom/upgraded_database/migrate_data`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:186 +msgid ":ref:`upgrade_custom/upgraded_database/test_custom`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:191 +msgid "Migrate the data" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:193 +msgid "During the upgrade of the custom modules, you might have to use migration scripts to reflect changes from the source code to their corresponding data." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:196 +msgid "Any technical data that was renamed during the upgrade of the custom code (models, fields, external identifiers) should be renamed using migration scripts to avoid data loss during the module upgrade." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:199 +msgid "Data from standard models removed from the source code of the newer Odoo version and from the database during the standard upgrade process might need to be recovered from the old model table if it is still present." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:203 +msgid "Migration scripts can also be used to:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:205 +msgid "Ease the processing time of an upgrade. For example, to store the value of computed stored fields on models with an excessive number of records by using SQL queries." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:207 +msgid "Recompute fields in case the computation of their value has changed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:208 +msgid "Uninstall unwanted custom modules." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:209 +msgid "Correct faulty data or wrong configurations." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:214 +msgid "Test the custom modules" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:216 +msgid "To make sure the custom modules work properly with your data in the upgraded database, they need to be tested as well. This helps ensure both the standard and the custom data stored in the database are consistent and that nothing was lost during the upgrade process." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:220 +msgid "Things to pay attention to:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:222 +msgid "Views not working: During the upgrade, if a view causes issues because of its content, it gets disabled. You can find the information on disabled views on the :ref:`Upgrade report `. This view needs to be activated again. To achieve this, we recommend the use of migration scripts." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:226 +msgid ":doc:`Module data <../tutorials/define_module_data>` not updated: Custom records that have the ``noupdate`` flag are not updated when upgrading the module in the new database. For the custom data that needs to be updated due to changes in the new version, we recommend to use migration scripts to do so." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:235 +msgid "Step 5: Testing and rehearsal" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:237 +msgid "When the custom modules are working properly in the upgraded database, it is crucial to do another round of testing to assess the database usability and detect any issues that might have gone unnoticed in previous tests. For further information about testing the upgraded database, check :ref:`upgrade/test_your_db`." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:242 +msgid "As mentioned in :ref:`upgrade/upgrade-prod`, both standard upgrade scripts and your database are constantly evolving. Therefore it is highly recommended to frequently request new upgraded test databases and ensure that the upgrade process is still successful." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:246 +msgid "In addition to that, make a full rehearsal of the upgrade process the day before upgrading the production database to avoid undesired behavior during the upgrade and to detect any issue that might have occurred with the migrated data." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:254 +msgid "Step 6: Production upgrade" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:256 +msgid "Once you are confident about upgrading your production database, follow the process described on :ref:`upgrade/upgrade-prod`, depending on the hosting type of your database." +msgstr "" + #: ../../content/developer/howtos/web_services.rst:3 msgid "Web Services" msgstr "" @@ -4186,7 +4533,7 @@ msgid ":option:`--addons-path `" msgstr "" #: ../../content/developer/howtos/website_themes/setup.rst:213 -#: ../../content/developer/reference/cli.rst:807 +#: ../../content/developer/reference/cli.rst:829 msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules." msgstr "" @@ -14114,435 +14461,447 @@ msgid "Logging" msgstr "" #: ../../content/developer/reference/cli.rst:472 -msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." +msgid "By default, Odoo displays all logging of level_ ``INFO``, ``WARNING`` and ``ERROR``. All logs independently of the level are output on ``stderr``. Various options are available to redirect logging to other destinations and to customize the verbosity." msgstr "" -#: ../../content/developer/reference/cli.rst:479 -msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" +#: ../../content/developer/reference/cli.rst:478 +msgid "sends logging output to the specified file instead of ``stderr``. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" msgstr "" -#: ../../content/developer/reference/cli.rst:486 +#: ../../content/developer/reference/cli.rst:485 msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." msgstr "" -#: ../../content/developer/reference/cli.rst:489 +#: ../../content/developer/reference/cli.rst:488 msgid "Neither is configurable" msgstr "" -#: ../../content/developer/reference/cli.rst:493 +#: ../../content/developer/reference/cli.rst:492 msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." msgstr "" -#: ../../content/developer/reference/cli.rst:499 +#: ../../content/developer/reference/cli.rst:498 msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." msgstr "" -#: ../../content/developer/reference/cli.rst:503 +#: ../../content/developer/reference/cli.rst:502 msgid "The colon ``:`` is mandatory" msgstr "" -#: ../../content/developer/reference/cli.rst:504 +#: ../../content/developer/reference/cli.rst:503 msgid "The logger can be omitted to configure the root (default) handler" msgstr "" -#: ../../content/developer/reference/cli.rst:505 +#: ../../content/developer/reference/cli.rst:504 msgid "If the level is omitted, the logger is set to ``INFO``" msgstr "" -#: ../../content/developer/reference/cli.rst:507 +#: ../../content/developer/reference/cli.rst:506 msgid "The option can be repeated to configure multiple loggers e.g." msgstr "" -#: ../../content/developer/reference/cli.rst:515 +#: ../../content/developer/reference/cli.rst:514 msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:520 +#: ../../content/developer/reference/cli.rst:519 msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:525 +#: ../../content/developer/reference/cli.rst:524 msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)." msgstr "" -#: ../../content/developer/reference/cli.rst:530 +#: ../../content/developer/reference/cli.rst:529 msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:" msgstr "" -#: ../../content/developer/reference/cli.rst:535 +#: ../../content/developer/reference/cli.rst:534 msgid "``debug_sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:534 +#: ../../content/developer/reference/cli.rst:533 msgid "sets the SQL logger to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:536 +#: ../../content/developer/reference/cli.rst:535 msgid "equivalent to ``--log-sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:539 +#: ../../content/developer/reference/cli.rst:538 msgid "``debug_rpc``" msgstr "" -#: ../../content/developer/reference/cli.rst:538 +#: ../../content/developer/reference/cli.rst:537 msgid "sets the ``odoo`` and HTTP request loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:540 +#: ../../content/developer/reference/cli.rst:539 msgid "equivalent to ``--log-level debug --log-request``" msgstr "" -#: ../../content/developer/reference/cli.rst:545 +#: ../../content/developer/reference/cli.rst:544 msgid "``debug_rpc_answer``" msgstr "" -#: ../../content/developer/reference/cli.rst:542 +#: ../../content/developer/reference/cli.rst:541 msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:545 +#: ../../content/developer/reference/cli.rst:544 msgid "equivalent to ``--log-level debug --log-request --log-response``" msgstr "" -#: ../../content/developer/reference/cli.rst:549 +#: ../../content/developer/reference/cli.rst:548 msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used" msgstr "" -#: ../../content/developer/reference/cli.rst:555 +#: ../../content/developer/reference/cli.rst:554 msgid "Multiprocessing" msgstr "" -#: ../../content/developer/reference/cli.rst:559 +#: ../../content/developer/reference/cli.rst:558 msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)." msgstr "" -#: ../../content/developer/reference/cli.rst:563 +#: ../../content/developer/reference/cli.rst:562 msgid "multiprocessing mode is only available on Unix-based systems" msgstr "" -#: ../../content/developer/reference/cli.rst:565 +#: ../../content/developer/reference/cli.rst:564 msgid "A number of options allow limiting and recycling workers:" msgstr "" -#: ../../content/developer/reference/cli.rst:569 +#: ../../content/developer/reference/cli.rst:568 msgid "Number of requests a worker will process before being recycled and restarted." msgstr "" -#: ../../content/developer/reference/cli.rst:572 +#: ../../content/developer/reference/cli.rst:571 msgid "Defaults to *8196*." msgstr "" -#: ../../content/developer/reference/cli.rst:576 +#: ../../content/developer/reference/cli.rst:575 msgid "Maximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request." msgstr "" -#: ../../content/developer/reference/cli.rst:579 +#: ../../content/developer/reference/cli.rst:578 msgid "Defaults to *2048MiB (2048\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:583 +#: ../../content/developer/reference/cli.rst:582 msgid "Hard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing." msgstr "" -#: ../../content/developer/reference/cli.rst:587 +#: ../../content/developer/reference/cli.rst:586 msgid "Defaults to *2560MiB (2560\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:591 +#: ../../content/developer/reference/cli.rst:590 msgid "Prevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:594 +#: ../../content/developer/reference/cli.rst:593 msgid "Defaults to *60*." msgstr "" -#: ../../content/developer/reference/cli.rst:598 +#: ../../content/developer/reference/cli.rst:597 msgid "Prevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:601 +#: ../../content/developer/reference/cli.rst:600 msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries." msgstr "" -#: ../../content/developer/reference/cli.rst:604 +#: ../../content/developer/reference/cli.rst:603 msgid "Defaults to *120*." msgstr "" -#: ../../content/developer/reference/cli.rst:608 +#: ../../content/developer/reference/cli.rst:607 msgid "number of workers dedicated to :ref:`cron ` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode." msgstr "" -#: ../../content/developer/reference/cli.rst:611 +#: ../../content/developer/reference/cli.rst:610 msgid "For multi-processing mode, this is in addition to the HTTP worker processes." msgstr "" -#: ../../content/developer/reference/cli.rst:616 +#: ../../content/developer/reference/cli.rst:615 msgid "Configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:620 +#: ../../content/developer/reference/cli.rst:619 msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``." msgstr "" -#: ../../content/developer/reference/cli.rst:625 +#: ../../content/developer/reference/cli.rst:624 msgid "Some conversions don't match the pattern:" msgstr "" -#: ../../content/developer/reference/cli.rst:627 +#: ../../content/developer/reference/cli.rst:626 msgid ":option:`--db-filter` becomes ``dbfilter``" msgstr "" -#: ../../content/developer/reference/cli.rst:628 +#: ../../content/developer/reference/cli.rst:627 msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean" msgstr "" -#: ../../content/developer/reference/cli.rst:629 +#: ../../content/developer/reference/cli.rst:628 msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:632 +#: ../../content/developer/reference/cli.rst:631 msgid ":option:`--smtp` is stored as ``smtp_server``" msgstr "" -#: ../../content/developer/reference/cli.rst:633 +#: ../../content/developer/reference/cli.rst:632 msgid ":option:`--database` is stored as ``db_name``" msgstr "" -#: ../../content/developer/reference/cli.rst:634 +#: ../../content/developer/reference/cli.rst:633 msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files" msgstr "" -#: ../../content/developer/reference/cli.rst:639 +#: ../../content/developer/reference/cli.rst:638 msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config `. Specifying :option:`--save ` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``." msgstr "" -#: ../../content/developer/reference/cli.rst:645 +#: ../../content/developer/reference/cli.rst:644 msgid "Here is a sample file:" msgstr "" -#: ../../content/developer/reference/cli.rst:670 +#: ../../content/developer/reference/cli.rst:669 msgid "Shell" msgstr "" -#: ../../content/developer/reference/cli.rst:672 -msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm ` and its functionalities." +#: ../../content/developer/reference/cli.rst:671 +msgid "The Odoo command line also allows launching Odoo as a Python console environment, enabling direct interaction with the :ref:`orm ` and its functionalities." msgstr "" -#: ../../content/developer/reference/cli.rst:682 -msgid "Specify a preferred REPL to use in shell mode." +#: ../../content/developer/reference/cli.rst:680 +msgid "Adding an exclamation mark to all contacts' names:" msgstr "" -#: ../../content/developer/reference/cli.rst:688 +#: ../../content/developer/reference/cli.rst:696 +msgid "By default, the shell is running in transaction mode. This means that any change made to the database is rolled back when exiting the shell. To commit changes, use `env.cr.commit()`." +msgstr "" + +#: ../../content/developer/reference/cli.rst:701 +msgid "Specify a preferred REPL to use in shell mode. This shell is started with the `env` variable already initialized to be able to access the ORM and other Odoo modules." +msgstr "" + +#: ../../content/developer/reference/cli.rst:705 +msgid ":ref:`reference/orm/environment`" +msgstr "" + +#: ../../content/developer/reference/cli.rst:710 msgid "Scaffolding" msgstr "" -#: ../../content/developer/reference/cli.rst:692 +#: ../../content/developer/reference/cli.rst:714 msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." msgstr "" -#: ../../content/developer/reference/cli.rst:697 +#: ../../content/developer/reference/cli.rst:719 msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." msgstr "" -#: ../../content/developer/reference/cli.rst:705 +#: ../../content/developer/reference/cli.rst:727 msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)" msgstr "" -#: ../../content/developer/reference/cli.rst:710 +#: ../../content/developer/reference/cli.rst:732 msgid "directory in which to create the new module, defaults to the current directory" msgstr "" -#: ../../content/developer/reference/cli.rst:715 +#: ../../content/developer/reference/cli.rst:737 msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" msgstr "" -#: ../../content/developer/reference/cli.rst:719 +#: ../../content/developer/reference/cli.rst:741 msgid "This will create module *my_module* in directory */addons/*." msgstr "" -#: ../../content/developer/reference/cli.rst:724 +#: ../../content/developer/reference/cli.rst:746 msgid "Database Population" msgstr "" -#: ../../content/developer/reference/cli.rst:728 +#: ../../content/developer/reference/cli.rst:750 msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model `, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records." msgstr "" -#: ../../content/developer/reference/cli.rst:739 +#: ../../content/developer/reference/cli.rst:761 msgid "list of models for which the database should be filled" msgstr "" -#: ../../content/developer/reference/cli.rst:743 +#: ../../content/developer/reference/cli.rst:765 msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)." msgstr "" -#: ../../content/developer/reference/cli.rst:748 +#: ../../content/developer/reference/cli.rst:770 msgid ":ref:`reference/performance/populate`" msgstr "" -#: ../../content/developer/reference/cli.rst:753 +#: ../../content/developer/reference/cli.rst:775 msgid "Cloc" msgstr "" -#: ../../content/developer/reference/cli.rst:757 +#: ../../content/developer/reference/cli.rst:779 msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript, CSS, SCSS, or XML. This can be used as a rough metric for pricing maintenance of extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:762 +#: ../../content/developer/reference/cli.rst:784 msgid "Command-line options" msgstr "" -#: ../../content/developer/reference/cli.rst:767 +#: ../../content/developer/reference/cli.rst:789 msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database." msgstr "" -#: ../../content/developer/reference/cli.rst:769 +#: ../../content/developer/reference/cli.rst:791 msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)." msgstr "" -#: ../../content/developer/reference/cli.rst:772 +#: ../../content/developer/reference/cli.rst:794 msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:779 +#: ../../content/developer/reference/cli.rst:801 msgid ":ref:`reference/cmdline/cloc/database-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:784 +#: ../../content/developer/reference/cli.rst:806 msgid "Process the files in the provided path." msgstr "" -#: ../../content/developer/reference/cli.rst:787 +#: ../../content/developer/reference/cli.rst:809 msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:794 +#: ../../content/developer/reference/cli.rst:816 msgid "Multiple paths can be provided by repeating the option." msgstr "" -#: ../../content/developer/reference/cli.rst:801 +#: ../../content/developer/reference/cli.rst:823 msgid ":ref:`reference/cmdline/cloc/path-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:808 +#: ../../content/developer/reference/cli.rst:830 msgid "Required if the :option:`--database` option is used." msgstr "" -#: ../../content/developer/reference/cli.rst:813 +#: ../../content/developer/reference/cli.rst:835 msgid "Specify a configuration file to use in place of the :option:`--addons-path` option." msgstr "" -#: ../../content/developer/reference/cli.rst:822 +#: ../../content/developer/reference/cli.rst:844 msgid "Show the details of lines counted for each file." msgstr "" -#: ../../content/developer/reference/cli.rst:826 +#: ../../content/developer/reference/cli.rst:848 msgid "Processed files" msgstr "" -#: ../../content/developer/reference/cli.rst:831 +#: ../../content/developer/reference/cli.rst:853 msgid "With the :option:`--database` option" msgstr "" -#: ../../content/developer/reference/cli.rst:833 +#: ../../content/developer/reference/cli.rst:855 msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported. Finally, it counts the lines of code of Javascript, CSS, and SCSS files, and of QWeb views from imported modules." msgstr "" -#: ../../content/developer/reference/cli.rst:839 +#: ../../content/developer/reference/cli.rst:861 msgid "Some files are excluded from the count by default:" msgstr "" -#: ../../content/developer/reference/cli.rst:841 +#: ../../content/developer/reference/cli.rst:863 msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)" msgstr "" -#: ../../content/developer/reference/cli.rst:842 +#: ../../content/developer/reference/cli.rst:864 msgid "The contents of the folder :file:`static/lib`" msgstr "" -#: ../../content/developer/reference/cli.rst:843 +#: ../../content/developer/reference/cli.rst:865 msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`" msgstr "" -#: ../../content/developer/reference/cli.rst:844 +#: ../../content/developer/reference/cli.rst:866 msgid "The migrations scripts defined in the folder :file:`migrations` and `upgrades`" msgstr "" -#: ../../content/developer/reference/cli.rst:845 +#: ../../content/developer/reference/cli.rst:867 msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest" msgstr "" -#: ../../content/developer/reference/cli.rst:847 +#: ../../content/developer/reference/cli.rst:869 msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:" msgstr "" -#: ../../content/developer/reference/cli.rst:860 +#: ../../content/developer/reference/cli.rst:882 msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs." msgstr "" -#: ../../content/developer/reference/cli.rst:862 +#: ../../content/developer/reference/cli.rst:884 msgid "For more information about the pattern syntax, see `glob `_." msgstr "" -#: ../../content/developer/reference/cli.rst:867 +#: ../../content/developer/reference/cli.rst:889 msgid "With the :option:`--path` option" msgstr "" -#: ../../content/developer/reference/cli.rst:869 +#: ../../content/developer/reference/cli.rst:891 msgid "This method works the same as with the :ref:`--database option ` if a manifest file is present in the given folder. Otherwise, it counts all files." msgstr "" -#: ../../content/developer/reference/cli.rst:875 +#: ../../content/developer/reference/cli.rst:897 msgid "Identifying Extra Modules" msgstr "" -#: ../../content/developer/reference/cli.rst:877 +#: ../../content/developer/reference/cli.rst:899 msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:884 +#: ../../content/developer/reference/cli.rst:906 #: ../../content/developer/reference/frontend/services.rst:662 msgid "Error Handling" msgstr "" -#: ../../content/developer/reference/cli.rst:886 +#: ../../content/developer/reference/cli.rst:908 msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output." msgstr "" -#: ../../content/developer/reference/cli.rst:890 +#: ../../content/developer/reference/cli.rst:912 msgid "Max file size exceeded" msgstr "" -#: ../../content/developer/reference/cli.rst:892 +#: ../../content/developer/reference/cli.rst:914 msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:" msgstr "" -#: ../../content/developer/reference/cli.rst:895 +#: ../../content/developer/reference/cli.rst:917 msgid "A generated XML file that contains lots of data. It should be excluded in the manifest." msgstr "" -#: ../../content/developer/reference/cli.rst:896 +#: ../../content/developer/reference/cli.rst:918 msgid "A JavaScript library that should be placed in the :file:`static/lib` folder." msgstr "" -#: ../../content/developer/reference/cli.rst:899 +#: ../../content/developer/reference/cli.rst:921 msgid "Syntax Error" msgstr "" -#: ../../content/developer/reference/cli.rst:901 +#: ../../content/developer/reference/cli.rst:923 msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``." msgstr "" -#: ../../content/developer/reference/cli.rst:908 +#: ../../content/developer/reference/cli.rst:930 msgid "TSConfig Generator" msgstr "" -#: ../../content/developer/reference/cli.rst:912 +#: ../../content/developer/reference/cli.rst:934 msgid "When working on javascript, there are ways to help your editor providing you with powerful auto-completion. One of those ways is the use of a tsconfig.json file. Originally meant for typescript, editors can use its information with plain javascript also. With this config file, you will now have full auto-completion across modules." msgstr "" -#: ../../content/developer/reference/cli.rst:917 +#: ../../content/developer/reference/cli.rst:939 msgid "The command to generate this files takes as many unnamed arguments as you need. Those are relative paths to your addon directories. In the example below, we move up one folder to save the tsconfig file in the folder containing community and enterprise." msgstr "" @@ -28856,7 +29215,7 @@ msgid "the content of the inheritance spec should be ``attribute`` elements with msgstr "" #: ../../content/developer/reference/user_interface/view_records.rst:299 -msgid "if the ``attribute`` element has a body, a new attributed named after its ``name`` is created on the matched node with the ``attribute`` element's text as value" +msgid "if the ``attribute`` element has a body, a new attribute named after its ``name`` is created on the matched node with the ``attribute`` element's text as value" msgstr "" #: ../../content/developer/reference/user_interface/view_records.rst:302 @@ -29774,10 +30133,6 @@ msgstr "" msgid "The value of a computed field usually depends on the values of other fields on the computed record. The ORM expects the developer to specify those dependencies on the compute method with the decorator :func:`~odoo.api.depends`. The given dependencies are used by the ORM to trigger the recomputation of the field whenever some of its dependencies have been modified::" msgstr "" -#: ../../content/developer/tutorials/backend.rst:716 -msgid "Computed fields" -msgstr "" - #: ../../content/developer/tutorials/backend.rst:718 msgid "Add the percentage of taken seats to the *Session* model" msgstr "" @@ -34004,7 +34359,7 @@ msgid "One could argue that we can already do these things by changing the state msgstr "" #: ../../content/developer/tutorials/getting_started/10_actions.rst:20 -msgid "Action Type" +msgid "Object Type" msgstr "" #: ../../content/developer/tutorials/getting_started/10_actions.rst:22 @@ -34112,7 +34467,7 @@ msgid "Pay attention: in real life only one offer can be accepted for a given pr msgstr "" #: ../../content/developer/tutorials/getting_started/10_actions.rst:126 -msgid "Object Type" +msgid "Action Type" msgstr "" #: ../../content/developer/tutorials/getting_started/10_actions.rst:128 diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 719fc14423..c1287cf050 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -118,7 +118,9 @@ msgid "The **Partner Ledger** report displays the balance of your customers and msgstr "" #: ../../content/applications/finance/accounting.rst:127 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:77 #: ../../content/applications/finance/accounting/reporting.rst:5 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:77 msgid "Reporting" msgstr "" @@ -128,7 +130,7 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:133 #: ../../content/applications/finance/fiscal_localizations/austria.rst:28 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1161 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1157 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -288,27 +290,27 @@ msgstr "" msgid "Retained earnings are the portion of income retained by a business. Odoo calculates current year earnings in real-time, so no year-end journal or rollover is required. The profit and loss balance is automatically reported on the balance sheet report." msgstr "" -#: ../../content/applications/finance/accounting.rst:225 +#: ../../content/applications/finance/accounting.rst:227 msgid "Fiduciaries" msgstr "" -#: ../../content/applications/finance/accounting.rst:227 +#: ../../content/applications/finance/accounting.rst:229 msgid "The :guilabel:`Accounting Firms` mode can be activated by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Firms mode`. When enabled:" msgstr "" -#: ../../content/applications/finance/accounting.rst:230 +#: ../../content/applications/finance/accounting.rst:232 msgid "The document's sequence becomes editable on all documents;" msgstr "" -#: ../../content/applications/finance/accounting.rst:231 +#: ../../content/applications/finance/accounting.rst:233 msgid "The :guilabel:`Total (tax incl.)` field appears to speed up and control the encoding by automating line creation with the right account and tax;" msgstr "" -#: ../../content/applications/finance/accounting.rst:233 +#: ../../content/applications/finance/accounting.rst:235 msgid ":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when encoding a transaction." msgstr "" -#: ../../content/applications/finance/accounting.rst:234 +#: ../../content/applications/finance/accounting.rst:236 msgid "A :guilabel:`Quick encoding` option is available for customer invoices and vendor bills." msgstr "" @@ -409,8 +411,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:27 #: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:14 #: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:13 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:29 #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:63 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:109 #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 @@ -421,28 +423,33 @@ msgstr "" #: ../../content/applications/finance/accounting/payments/batch.rst:11 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 #: ../../content/applications/finance/accounting/payments/follow_up.rst:14 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:12 #: ../../content/applications/finance/accounting/payments/online.rst:21 #: ../../content/applications/finance/accounting/payments/pay_checks.rst:10 #: ../../content/applications/finance/accounting/payments/pay_sepa.rst:45 #: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:10 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 -#: ../../content/applications/finance/accounting/taxes.rst:53 +#: ../../content/applications/finance/accounting/taxes.rst:51 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:14 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:17 #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 -#: ../../content/applications/finance/accounting/taxes/retention.rst:23 +#: ../../content/applications/finance/accounting/taxes/retention.rst:11 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:18 #: ../../content/applications/finance/documents.rst:16 #: ../../content/applications/finance/fiscal_localizations.rst:21 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 -#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:8 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:329 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:424 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:878 #: ../../content/applications/finance/fiscal_localizations/austria.rst:6 #: ../../content/applications/finance/fiscal_localizations/austria.rst:45 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:370 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:570 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 @@ -730,7 +737,7 @@ msgid "If your connection with the proxy is disconnected, you can reconnect with msgstr "" #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:110 -msgid "This disconnection can be caused by the Odoo support. In this case, please contact the `support `_ directly with your client id or the reference of the error listed in the chatter." +msgid "If you are unable to reconnect using the :guilabel:`Reconnect` button, please contact the `support `_ directly with your client id or the reference of the error listed in the chatter." msgstr "" #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:117 @@ -1336,7 +1343,7 @@ msgid "Unrealized Currency Gains/Losses report once adjusted." msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:3 -#: ../../content/applications/finance/accounting/payments/batch.rst:55 +#: ../../content/applications/finance/accounting/payments/batch.rst:52 msgid "Bank reconciliation" msgstr "" @@ -1885,10 +1892,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:107 #: ../../content/applications/finance/accounting/customer_invoices.rst:128 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:52 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:69 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:119 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:139 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:56 msgid "**Account**" msgstr "" @@ -1904,10 +1909,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:107 #: ../../content/applications/finance/accounting/customer_invoices.rst:128 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:53 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:120 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:140 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:40 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 @@ -1916,10 +1919,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:107 #: ../../content/applications/finance/accounting/customer_invoices.rst:128 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:54 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:71 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:121 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:141 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 @@ -1955,8 +1956,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:167 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:180 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:380 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:366 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:376 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 #: ../../content/applications/finance/fiscal_localizations/peru.rst:73 @@ -1974,6 +1975,12 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:113 #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:142 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:146 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:150 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:154 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:158 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:162 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 @@ -1989,7 +1996,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 -#: ../../content/applications/finance/accounting/taxes.rst:127 +#: ../../content/applications/finance/accounting/taxes.rst:112 msgid "100" msgstr "" @@ -2111,7 +2118,7 @@ msgid ":doc:`payment_terms`" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:22 -#: ../../content/applications/finance/accounting/payments/batch.rst:71 +#: ../../content/applications/finance/accounting/payments/batch.rst:67 msgid ":doc:`../payments`" msgstr "" @@ -2552,258 +2559,308 @@ msgid "Deferred revenues" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:5 -msgid "**Deferred revenues**, or **unearned revenue**, are payments made in advance by customers for products yet to deliver or services yet to render." +msgid "**Deferred revenues**, or **unearned revenues**, are invoices addressed to customers for goods yet to be delivered or services yet to be rendered." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:8 -msgid "Such payments are a **liability** for the company that receives them since it still owes its customers these products or services. The company cannot report them on the current **Profit and Loss statement**, or *Income Statement*, since the payments will be effectively earned in the future." +msgid "The company cannot report them on the current **profit and loss statement**, or *income statement*, since the goods and services will be effectively delivered/rendered in the future." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:12 -msgid "These future revenues must be deferred on the company's balance sheet until the moment in time they can be **recognized**, at once or over a defined period, on the Profit and Loss statement." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:11 +msgid "These future revenues must be deferred on the company's balance sheet among the current liabilities until they can be **recognized**, at once or over a defined period, on the profit and loss statement." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:15 -msgid "For example, let's say we sell a five-year extended warranty for $ 350. We already receive the money now but haven't earned it yet. Therefore, we post this new income in a deferred revenue account and decide to recognize it on a yearly basis. Each year, for the next 5 years, $ 70 will be recognized as revenue." +msgid "For example, let's say a business sells a software license of $1200 for 1 year. They immediately invoice it to the customer but can't consider it earned yet, as the future months of licensing have not yet been delivered. Therefore, they post this new revenue in a deferred revenue account and recognize it on a monthly basis. Each month, for the next 12 months, $100 will be recognized as revenue." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:20 -msgid "Odoo Accounting handles deferred revenues by spreading them in multiple entries that are automatically created in *draft mode* and then posted periodically." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:21 +msgid "Odoo Accounting handles deferred revenues by spreading them in multiple entries that are posted periodically." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:24 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:25 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:25 -msgid "The server checks once a day if an entry must be posted. It might then take up to 24 hours before you see a change from *draft* to *posted*." +msgid "The server checks once a day if an entry must be posted. It might then take up to 24 hours before you see a change from :guilabel:`Draft` to :guilabel:`Posted`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:28 -#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 -msgid "Prerequisites" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:31 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:31 +msgid "Make sure the default settings are correctly configured for your business. To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. The following options are available:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:30 -msgid "Such transactions must be posted on a **Deferred Revenue Account** rather than on the default income account." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:34 +msgid "Journal" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 -msgid "Configure a Deferred Revenue Account" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:35 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:35 +msgid "The deferral entries are posted in this journal." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:36 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:36 +msgid "Deferred Expense Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:37 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:37 -msgid "To configure your account in the **Chart of Accounts**, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." +msgid "Expenses are deferred on this Current Asset account until they are recognized." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Configuration of a Deferred Revenue Account in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:38 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:38 +msgid "Deferred Revenue Account" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:44 -msgid "This account's type must be either *Current Liabilities* or *Non-current Liabilities*" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:39 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:39 +msgid "Revenues are deferred on this Current Liability account until they are recognized." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:47 -msgid "Post an income to the right account" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:43 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:43 +msgid "Generate Entries" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:50 -msgid "Select the account on a draft invoice" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:41 +msgid "By default, Odoo :ref:`automatically generates ` the deferral entries when you post a customer invoice. However, you can also choose to :ref:`generate them manually ` by selecting the :guilabel:`Manually & Grouped` option instead." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:52 -msgid "On a draft invoice, select the right account for all the products of which the incomes must be deferred." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:48 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:48 +msgid "Amount Computation" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Selection of a Deferred Revenue Account on a draft invoice in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:46 +msgid "Suppose an invoice of $1200 must be deferred over 12 months. The :guilabel:`Equal per month` computation accounts for $100 each month, while the :guilabel:`Based on days` computation accounts for different amounts depending on the number of days in each month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:53 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:53 +msgid "Generate deferral entries on validation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:56 +msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Invoice Date`." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 -msgid "Choose a different Income Account for specific products" +msgid "For each line of the invoice that should be deferred, specify the start and end dates of the deferral period." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:62 -msgid "Start editing the product, go to the *Accounting* tab, select the right **Income Account**, and save." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:63 +msgid "If the :guilabel:`Generate Entries` field in the **Settings** is set to :guilabel:`On invoice/bill validation`, Odoo automatically generates the deferral entries when the invoice is validated. Click the :guilabel:`Deferred Entries` smart button to see them." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Change of the Income Account for a product in Odoo" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:67 +msgid "One entry, dated on the same day as the invoice, moves the invoice amounts from the income account to the deferred account. The other entries are deferral entries which, month after month, move the invoice amounts from the deferred account to the income account to recognize the revenue." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:70 -msgid "It is possible to automate the creation of revenue entries for these products (see: `Automate the Deferred Revenues`_)." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:72 +msgid "You can defer a January invoice of $1200 over 12 months by specifying a start date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800 is recognized as an income, whereas $400 remains on the deferred account." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:74 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:75 -msgid "Change the account of a posted journal item" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:79 +msgid "The deferred revenue report computes an overview of the necessary deferral entries for each account. To access it, go to :menuselection:`Accounting --> Reporting --> Deferred Revenue`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:76 -msgid "To do so, open your Sales Journal by going to :menuselection:`Accounting --> Accounting --> Sales`, select the journal item you want to modify, click on the account, and select the right one." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:82 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:82 +msgid "To view the journal items of each account, click on the account name and then :guilabel:`Journal Items`." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:-1 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Modification of a posted journal item's account in Odoo Accounting" +msgid "Deferred revenue report" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:85 -msgid "Deferred Revenues entries" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:89 +msgid "Only invoices whose accounting date is before the end of the period of the report are taken into account." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:88 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:89 -msgid "Create a new entry" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:95 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:95 +msgid "Generate grouped deferral entries manually" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:90 -msgid "A **Deferred Revenues entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time until the full amount of the income is recognized." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:97 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 +msgid "If you have a lot of deferred revenues and wish to reduce the number of journal entries created, you can generate deferral entries manually. To do so, set the :guilabel:`Generate Entries` field in the **Settings** to :guilabel:`Manually & Grouped`. Odoo then aggregates the deferred amounts in a single entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:93 -msgid "To create a new entry, go to :menuselection:`Accounting --> Accounting --> Deferred Revenues`, click on *Create*, and fill out the form." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:102 +msgid "At the end of each month, go to :menuselection:`Accounting --> Reporting --> Deferred Revenue` and click the :guilabel:`Generate Entries` button. This generates two deferral entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:96 -msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Sales** tab." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:105 +msgid "One dated at the end of the month which aggregates, for each account, all the deferred amounts of that month. This means that a part of the deferred revenue is recognized at the end of that period." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Deferred Revenue entry in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:108 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:108 +msgid "The reversal of this created entry, dated on the following day (i.e., the first day of the next month) to cancel the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:104 -msgid "Once done, you can click on *Compute Revenue* (next to the *Confirm* button) to generate all the values of the **Revenue Board**. This board shows you all the entries that Odoo will post to recognize your revenue, and at which date." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:112 +msgid "There are two invoices:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Revenue Board in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:114 +msgid "Invoice A: $1200 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:113 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:114 -msgid "What does \"Prorata Temporis\" mean?" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 +msgid "Invoice B: $600 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 -msgid "The **Prorata Temporis** feature is useful to recognize your revenue the most accurately possible." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "In January" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:117 -msgid "With this feature, the first entry on the Revenue Board is computed based on the time left between the *Prorata Date* and the *First Recognition Date* rather than the default amount of time between recognitions." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:118 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:119 +msgid "At the end of January, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:121 -msgid "For example, the Revenue Board above has its first revenue with an amount of $ 4.22 rather than $ 70.00. Consequently, the last entry is also lower and has an amount of $ 65.78." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:122 +msgid "Entry 1 dated on the 31st January:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:123 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:140 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:156 +msgid "Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both invoices)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:124 +msgid "Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of invoice A and invoice B)" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 -msgid "Deferred Entry from the Sales Journal" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +msgid "Line 3: Deferred account 1800 - 150 = **1650** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:127 -msgid "You can create a deferred entry from a specific journal item in your **Sales Journal**." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:128 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:129 +msgid "Entry 2 dated on the 1st February, the reversal of the previous entry:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:129 -msgid "To do so, open your Sales Journal by going to :menuselection:`Accounting --> Accounting --> Sales`, and select the journal item you want to defer. Make sure that it is posted in the right account (see: `Change the account of a posted journal item`_)." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:130 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:131 +msgid "Line 1: Expense account **1800**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:134 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:134 -msgid "Then, click on *Action*, select **Create Deferred Entry**, and fill out the form the same way you would do to `create a new entry`_." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:131 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:132 +msgid "Line 2: Deferred account **-150**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Create Deferred Entry from a journal item in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "Line 3: Expense account **-1650**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 -msgid "Deferred Revenue Models" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "In February" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:144 -msgid "You can create **Deferred Revenue Models** to create your Deferred Revenue entries faster." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:135 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:136 +msgid "At the end of February, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:146 -msgid "To create a model, go to :menuselection:`Accounting --> Configuration --> Deferred Revenue Models`, click on *Create*, and fill out the form the same way you would do to create a new entry." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:138 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:139 +msgid "Entry 1 dated on the 28th February:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:150 -msgid "You can also convert a *confirmed Deferred Revenue entry* into a model by opening it from :menuselection:`Accounting --> Accounting --> Deferred Revenues` and then, by clicking on the button *Save Model*." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:141 +msgid "Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of invoice A and invoice B)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:155 -msgid "Apply a Deferred Revenue Model to a new entry" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:143 +msgid "Line 3: Deferred account 1800 - 300 = **1500** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 -msgid "When you create a new Deferred Revenue entry, fill out the **Deferred Revenue Account** with the right recognition account." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "Entry 2 dated on the 1st March, the reversal of the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:160 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:160 -msgid "New buttons with all the models linked to that account appear at the top of the form. Clicking on a model button fills out the form according to that model." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "From March to October" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Deferred Revenue model button in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "The same computation is done for each month until October." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:170 -msgid "Automate the Deferred Revenues" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "In November" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 -msgid "When you create or edit an account of which the type is either *Current Liabilities* or *Non-current Liabilities*, you can configure it to defer the revenues that are credited on it automatically." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:151 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:152 +msgid "At the end of November, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 -msgid "You have three choices for the **Automate Deferred Revenue** field:" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:154 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:155 +msgid "Entry 1 dated on the 30th November:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:177 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:177 -msgid "**No:** this is the default value. Nothing happens." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 +msgid "Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of invoice A and invoice B)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:178 -msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Deferred Revenues entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Deferred Revenues`." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:159 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:159 +msgid "Line 3: Deferred account 1800 - 1650 = **150** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:181 -msgid "**Create and validate:** you must also select a Deferred Revenue Model (see: `Deferred Revenue Models`_). Whenever a transaction is posted on the account, a *Deferred Revenues entry* is created and immediately validated." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "Entry 2 dated on the 1st December, the reversal of the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:-1 -msgid "Automate Deferred Revenue on an account in Odoo Accounting" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:166 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:166 +msgid "In December" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:190 -msgid "You can, for example, select this account as the default **Income Account** of a product to fully automate its sale. (see: `Choose a different Income Account for specific products`_)." +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:165 +msgid "There is no need to generate entries in December. Indeed, if we do the computation for December, we have an amount of 0 to be deferred." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:194 -#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:195 -msgid ":doc:`../get_started/chart_of_accounts`" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "In total" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:169 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:169 +msgid "If we aggregate everything, we would have:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:171 +msgid "invoice A and invoice B" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 +msgid "two entries (one for the deferral and one for the reversal) for each month from January to November" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:195 -msgid "`Odoo Academy: Deferred Revenues (Recognition) `_" +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +msgid "Therefore, at the end of December, invoices A and B are fully recognized as income only once in spite of all the created entries thanks to the reversal mechanism." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:3 @@ -2946,7 +3003,7 @@ msgid "Every PDF generated by Odoo includes an integrated **Factur-X** XML file. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:58 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 msgid ":doc:`../../fiscal_localizations`" @@ -2993,38 +3050,78 @@ msgid "Peppol" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:101 -msgid "The `Peppol `_ network ensures the exchange of documents and information between enterprises and governmental authorities. It is primarily used for electronic invoicing, and its access points (connectors to the Peppol network) allow enterprises to exchange electronic documents. Odoo is now an **access point** enabling electronic invoicing transactions without the need to send invoices and bills by email or post." +msgid "The `Peppol `_ network ensures the exchange of documents and information between enterprises and governmental authorities. It is primarily used for electronic invoicing, and its access points (connectors to the Peppol network) allow enterprises to exchange electronic documents." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:106 +msgid "Odoo is an **access point** and an :abbr:`SMP (Service Metadata Publisher)`, enabling electronic invoicing transactions without the need to send invoices and bills by email or post." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:109 +msgid "If not done yet, :ref:`install ` the :guilabel:`Peppol` module (`account_peppol`)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:112 +msgid "Peppol registration is **free** and available in Odoo Community" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:113 +msgid "You can send **Customer Invoices** and **Credit Notes** and receive **Vendor Bills** and **Refunds** via Peppol." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:115 +msgid "You can send in one of the following supported document formats: **BIS Billing 3.0, XRechnung CIUS, NLCIUS**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "The following **countries** are eligible for **Peppol registration in Odoo**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Andorra, Albania, Austria, Bosnia and Herzegovina, Belgium, Bulgaria, Switzerland, Cyprus, Czech Republic, Germany, Denmark, Estonia, Spain, Finland, France, United Kingdom, Greece, Croatia, Hungary, Ireland, Iceland, Italy, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Montenegro, North Macedonia, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Sweden, Slovenia, Slovakia, San Marino, Turkey, Holy See (Vatican City State)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:125 +msgid "Registration" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:111 -msgid "First, :ref:`install ` the :guilabel:`Peppol` module (`account_peppol`)." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:127 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. If you do not have the Peppol module installed, first tick the :guilabel:`Enable PEPPOL` checkbox and then **manually save**." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 -msgid "Peppol module install" +msgid "Peppol module installation" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:116 -msgid "Then, go to :menuselection:`Accounting --> Configuration --> Settings`, tick the :guilabel:`Use PEPPOL Invoicing`, and fill in the following information:" +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:134 +msgid "Fill in the following information:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:119 -msgid "`PEPPOL EAS `_" +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:136 +msgid ":guilabel:`Peppol EAS`. This is the Peppol Electronic Address Scheme and usually depends on your company's country. Odoo often prefills this with the most commonly used EAS code in your country. For example, the preferred EAS code for most companies in Belgium is 0208." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:120 -msgid ":guilabel:`Peppol Endpoint`" +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:139 +msgid ":guilabel:`Peppol Endpoint`. This is usually a Company Registry number or a VAT number." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:121 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:140 msgid ":guilabel:`Phone Number`, including the country code (e.g., `+32` in Belgium)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:122 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:141 msgid ":guilabel:`Primary contact email`" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:124 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:144 +msgid "`Peppol EAS - European Commision `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:145 +msgid "`Peppol Endpoint - OpenPeppol eDEC Code Lists `_ (open the \"Participant Identifier Schemes\" as HTML page)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:148 msgid "If you are migrating from another access point, insert the :guilabel:`Migration key` from the previous provider." msgstr "" @@ -3032,20 +3129,152 @@ msgstr "" msgid "Configuration for peppol" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:130 -msgid "Finally, click on :guilabel:`Validate registration`." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:154 +msgid "Finally, click :guilabel:`Validate registration`. If you want to explore or demo Peppol, you can choose to register in :guilabel:`Demo` mode. Otherwise, select :guilabel:`Live`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol demo mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:161 +msgid "When testing Peppol, the system parameter `account_peppol.edi.mode` can be changed to `test`. Then, a radio button appears with the option to register on the test server." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode parameter" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:170 +msgid "Now, you can request a verification code to be sent to you by clicking :guilabel:`Verify phone number`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "phone validation request verification" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:132 -msgid "A text message containing a code is sent to the phone number provided to finalize the registration process." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:176 +msgid "A text message containing a code is sent to the phone number provided to finalize the verification process." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 msgid "phone validation" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:138 -msgid "All invoices and vendor bills are now sent directly using the Peppol network." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:182 +msgid "Once you enter the code and click :guilabel:`Confirm`, you can see that your registration is pending activation. From this point onwards, the default journal for receiving Vendor Bills can be set." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "pending application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:188 +msgid "It should be automatically activated within a day." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:191 +msgid "It is also possible to manually trigger the cron that checks the registration status by going to :menuselection:`Settings --> Technical --> Scheduled Actions --> PEPPOL\\: update participant status`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:195 +msgid "Your application status should be updated soon after you are registered on the Peppol network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "active application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:200 +msgid "All invoices and vendor bills can now be sent directly using the Peppol network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:203 +msgid "Contact verification" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:205 +msgid "Before sending an invoice to a contact using the Peppol network, it is necessary to verify that they are also registered as a Peppol participant." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:208 +msgid "To do so, go to :menuselection:`Accounting --> Customers --> Customers` and open the customer's form. Then go to :menuselection:`Accounting tab --> Electronic Invoicing`, select the correct format, and make sure their :guilabel:`Peppol EAS code` and the :guilabel:`Endpoint` are filled in. Then, click :guilabel:`Verify`. If the contact exists on the network, their Peppol endpoint validity is set to Valid." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "verify contact registration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:218 +msgid "While Odoo prefills both the EAS code and the Endpoint number based on the information available for a contact, it is better to confirm these details directly with the contact." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:221 +msgid "It is possible to verify the Peppol participant status of several customers at once. To do so, go to :menuselection:`Accounting --> Customers --> Customers` and switch to the list view. Select the customers you want to verify and then click :menuselection:`Actions --> Verify Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:226 +msgid "Send invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:228 +msgid "Once ready to send an invoice via the Peppol network, simply click :guilabel:`Send & Print` on the invoice form. To queue multiple invoices, select them in the list view and click :menuselection:`Actions --> Send & Print`; they will be sent in a batch later on. Both :guilabel:`BIS Billing 3.0` and :guilabel:`Send via PEPPOL` checkboxes need to be ticked." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "Send peppol invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:236 +msgid "Posted invoices that can be sent via Peppol are marked as :guilabel:`Peppol Ready`. To display them, use the :guilabel:`Peppol Ready` filter or access the Accounting dashboard and click :guilabel:`Peppol ready invoices` on the corresponding sales journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "Filter Peppol ready invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:243 +msgid "Once the invoices are sent via Peppol, the status is changed to :guilabel:`Processing`. The status is changed to `Done` after they have been successfully delivered to the contact's Access Point." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "Peppol message status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:251 +msgid "By default, the Peppol status column is hidden on the Invoices list view. You can choose to have it displayed by selecting it from the optional columns, accessible from the top right corner of the Invoices list view." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:255 +msgid "A cron runs regularly to check the status of these invoices. It is possible to check the status before the cron runs by clicking :guilabel:`Fetch Peppol invoice status` in the corresponding sales journal on the Accounting dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "Fetch invoice Peppol status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:263 +msgid "Receive vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:265 +msgid "Once a day, a cron checks whether any new documents have been sent to you via the Peppol network. These documents are imported, and the corresponding vendor bills are created automatically as drafts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "peppol receive bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:272 +msgid "If you want to retrieve incoming Peppol documents before the cron runs, you can do so from the Accounting dashboard on the main Peppol purchase journal that you set up in the settings. Just click :guilabel:`Fetch from Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:-1 +msgid "Fetch bills from Peppol" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 @@ -3185,19 +3414,39 @@ msgstr "" msgid ":doc:`../reporting/intrastat`" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:33 -msgid "Define an Incoterm" +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:29 +msgid ":doc:`../customer_invoices`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:30 +msgid ":doc:`../vendor_bills`" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:35 +msgid "Define an Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:37 msgid "To define an Incoterm manually, create an invoice or bill, click the :guilabel:`Other Info` tab, and select the :guilabel:`Incoterm`." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:41 -msgid "Default Incoterm configuration" +msgid "Incoterm location" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:43 +msgid "A location relevant to the chosen Incoterm can be added to the invoice or bill under :guilabel:`Other Info` in the :guilabel:`Incoterm Location` field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:47 +msgid "If the chosen Incoterm code is `CIF` (Cost, Insurance, Freight), the associated location might be the destination port where the goods will be delivered." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:53 +msgid "Default Incoterm configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:55 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." msgstr "" @@ -3915,6 +4164,7 @@ msgid "You can also change these settings by going to :menuselection:`Accounting msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:99 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 msgid "Chart of Accounts" msgstr "" @@ -4751,7 +5001,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:146 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:365 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:361 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 @@ -4840,11 +5090,12 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 #: ../../content/applications/finance/accounting/reporting.rst:36 #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:27 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 msgid "Balance Sheet" msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 msgid "Assets" msgstr "" @@ -4949,66 +5200,62 @@ msgstr "" msgid "Off-Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 -msgid "Assets, deferred expenses, and deferred revenues automation" -msgstr "" - #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:98 -msgid "Some **account types** can **automate** the creation of :ref:`assets ` entries, :ref:`deferred expenses ` entries, and :ref:`deferred revenues ` entries. To **automate** entries, click :guilabel:`View` on an account line and go to the :guilabel:`Automation` tab." +msgid "Some **account types** can **automate** the creation of :ref:`asset ` entries. To **automate** entries, click :guilabel:`View` on an account line and go to the :guilabel:`Automation` tab." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:103 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:102 msgid "You have three choices for the :guilabel:`Automation` tab:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 msgid ":guilabel:`No`: this is the default value. Nothing happens." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:106 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created but not validated. You must first fill out the corresponding form." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:108 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 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." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:112 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 #: ../../content/applications/finance/accounting/taxes.rst:14 msgid "Default taxes" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:114 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 msgid "In the :guilabel:`View` menu of an account, select a **default tax** to be applied when this account is chosen for a product sale or purchase." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:118 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:117 #: ../../content/applications/finance/documents.rst:52 -#: ../../content/applications/finance/sign.rst:227 +#: ../../content/applications/finance/sign.rst:236 msgid "Tags" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:120 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:119 msgid "Some accounting reports require **tags** to be set on the relevant accounts. To add a tag, under :guilabel:`View`, click the :guilabel:`Tags` field and select an existing tag or :guilabel:`Create` a new one." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:125 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:124 msgid "Account groups" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:127 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 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:`View`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:134 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:133 msgid "Create account groups manually" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:137 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:136 msgid "Regular users should not need to create account groups manually. The following section is only intended for rare and advanced use cases." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:140 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:139 msgid "To create a new account group, activate :ref:`developer mode ` and head to :menuselection:`Accounting --> Configuration --> Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields." msgstr "" @@ -5016,7 +5263,7 @@ msgstr "" msgid "Account groups creation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:148 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:147 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`." msgstr "" @@ -5024,19 +5271,19 @@ msgstr "" msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:156 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:155 msgid "Allow reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:158 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:157 msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:161 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:160 msgid "For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with its payment. Therefore, the account used to record credit card payments needs to be configured as **allowing reconciliation**." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:165 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:164 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." msgstr "" @@ -5044,35 +5291,35 @@ msgstr "" msgid "Allow reconciliation for accounts in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:172 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:171 msgid "Deprecated" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:174 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:173 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`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 msgid ":doc:`cheat_sheet`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 msgid ":doc:`../vendor_bills/assets`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 msgid ":doc:`../vendor_bills/deferred_expenses`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 msgid ":doc:`../customer_invoices/deferred_revenues`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 msgid "`Odoo Tutorials: Chart of accounts `_" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:185 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 msgid "`Odoo Tutorials: Update your chart of accounts `_" msgstr "" @@ -5456,7 +5703,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:252 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:159 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:282 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:278 #: ../../content/applications/finance/fiscal_localizations/france.rst:194 #: ../../content/applications/finance/fiscal_localizations/india.rst:101 #: ../../content/applications/finance/fiscal_localizations/peru.rst:299 @@ -5609,15 +5856,15 @@ msgid "Payments" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:7 -msgid "In Odoo, payments can either be linked automatically to an invoice or bill or be stand-alone records for use at a later date." +msgid "In Odoo, payments can either be automatically linked to an invoice or bill or be stand-alone records for use at a later date:" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:10 -msgid "If a payment is **linked to an invoice or bill**, it reduces the amount due of the invoice. You can have multiple payments related to the same invoice." +msgid "If a payment is **linked to an invoice or bill**, it reduces/settles the amount due of the invoice. You can have multiple payments related to the same invoice." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:13 -msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with your company, or your company has an outstanding debit with a vendor. You can use those outstanding amounts to reduce unpaid invoices/bills." +msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with your company, or your company has an outstanding debit with a vendor. You can use those outstanding amounts to reduce/settle unpaid invoices/bills." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:18 @@ -5625,9 +5872,6 @@ msgid ":doc:`Internal transfers `" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:19 -#: ../../content/applications/finance/accounting/payments.rst:54 -#: ../../content/applications/finance/accounting/payments.rst:78 -#: ../../content/applications/finance/accounting/payments.rst:131 msgid ":doc:`bank/reconciliation`" msgstr "" @@ -5640,111 +5884,123 @@ msgid "Registering payment from an invoice or bill" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:26 -msgid "When clicking on :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the amount of the payment. The counterpart is reflected in an outstanding receipts or payments account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." +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 ` **receipts** or **payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:32 -msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking on :guilabel:`View`." +#: ../../content/applications/finance/accounting/payments.rst:33 +msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking :guilabel:`View`." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "See detailed information of a payment" +msgid "See detailed information of a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:39 -msgid "The customer invoice or vendor bill should be in the status :guilabel:`Posted` to register the payment." +#: ../../content/applications/finance/accounting/payments.rst:40 +msgid "The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:41 -msgid "When clicking on :guilabel:`Register payment`, you can select the amount to pay and make a partial or full payment." +#: ../../content/applications/finance/accounting/payments.rst:42 +msgid "If you unreconcile a payment, it still appears in your books but is no longer linked to the invoice." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:43 -msgid "If your main bank account is set as :ref:`outstanding account `, and the payment is made in Odoo (not related to a bank statement), invoices and bills are directly registered in the status :guilabel:`Paid`." +#: ../../content/applications/finance/accounting/payments.rst:44 +msgid "If you (un)reconcile a payment in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:46 -msgid "If you unreconciled a payment, it still appears in your books but is no longer linked to the invoice." -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:48 -msgid "If you (un)reconcile a payment in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount." +msgid "If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is automatically created to post the cash basis tax (reversal) amount." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:50 -msgid "If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is automatically created to post the cash basis tax (reversal) amount." +msgid "If your main bank account is set as an :ref:`outstanding account `, and the payment is registered in Odoo (not through a related bank statement), invoices and bills are directly registered as :guilabel:`Paid`." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:57 +#: ../../content/applications/finance/accounting/payments.rst:55 msgid "Registering payments not tied to an invoice or bill" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:59 -msgid "When a new payment is registered via the menu :menuselection:`Customers / Vendors --> Payments`, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable are matched with the outstanding account until they are manually matched with their related invoice or bill." +#: ../../content/applications/finance/accounting/payments.rst:57 +msgid "When a new payment is registered via :menuselection:`Customers / Vendors --> Payments` menu, 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." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:65 +#: ../../content/applications/finance/accounting/payments.rst:63 msgid "Matching invoices and bills with payments" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:67 -msgid "A blue banner appears when you validate a new invoice or bill and there is an outstanding payment for this specific customer or vendor. It can easily be matched from the invoice or the bill by clicking on :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." +#: ../../content/applications/finance/accounting/payments.rst:65 +msgid "A blue banner appears when you validate a new invoice/bill and an **outstanding payment** exists for this specific customer or vendor. It can easily be matched from the invoice or bill by clicking :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "Shows the ADD option to reconcile an invoice or a bill with a payment" +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:74 -msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with the bank statement." +#: ../../content/applications/finance/accounting/payments.rst:72 +msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its corresponding bank statement." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:83 +#: ../../content/applications/finance/accounting/payments.rst:78 msgid "Batch payment" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:85 -msgid "Batch payments allow you to group different payments to ease :doc:`reconciliation `. They are also useful when you deposit checks to the bank or for SEPA Payments. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select several payments and group them in a batch by clicking on :menuselection:`Action --> Create Batch Payment`." +#: ../../content/applications/finance/accounting/payments.rst:80 +msgid "Batch payments allow you to group different payments to ease :doc:`reconciliation `. They are also useful when you deposit :doc:`checks ` to the bank or for :doc:`SEPA payments `. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select and group several payments in a batch by clicking :menuselection:`Action --> Create Batch Payment`." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:93 +#: ../../content/applications/finance/accounting/payments.rst:88 msgid ":doc:`payments/batch`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:94 +#: ../../content/applications/finance/accounting/payments.rst:89 msgid ":doc:`payments/batch_sdd`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:99 +#: ../../content/applications/finance/accounting/payments.rst:94 msgid "Payments matching" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:101 -msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and gives you the opportunity to process them all one by one, doing the matching of all their payments and invoices at once. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, and click on :guilabel:`⋮` and select :guilabel:`Payments Matching`, or by going to :menuselection:`Accounting --> Reconciliation`." +#: ../../content/applications/finance/accounting/payments.rst:96 +msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and allows you to process them individually, matching all payments and invoices in one place. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting --> Reconciliation`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:-1 +msgid "Payments matching menu in the drop-down menu." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:108 +#: ../../content/applications/finance/accounting/payments.rst:106 msgid "During the :doc:`reconciliation `, if the sum of the debits and credits does not match, there is a remaining balance. This either needs to be reconciled at a later date or needs to be written off directly." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:113 +#: ../../content/applications/finance/accounting/payments.rst:111 msgid "Batch payments matching" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:115 -msgid "To reconcile several outstanding payments or invoices at once, for a specific customer or vendor, the batch reconciliation feature can be used. Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged Payable`. You now see all transactions that have not been reconciled yet, and when you select a customer or vendor, the :guilabel:`Reconcile` option is displayed." +#: ../../content/applications/finance/accounting/payments.rst:113 +msgid "You can use the **batch reconciliation feature** to reconcile several outstanding payments or invoices simultaneously for a specific customer or vendor. Go to your **Accounting Dashboard** and open your **bank journal**. In the **bank reconciliation** view, select a **transaction**, and click the :guilabel:`Batch Payments` tab. From here, you can reconcile your :doc:`batch payments ` with your outstanding payments or invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:-1 +msgid "The batch payment reconcile option." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:123 +msgid "Registering a partial payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:125 +msgid "To register a **partial payment**, click :guilabel:`Register payment` from the related invoice or bill, and enter the amount received or paid. Upon entering the amount, a prompt appears to decide whether to :guilabel:`Keep open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select :guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or bill is now marked as :guilabel:`Partial`. Select :guilabel:`Mark as fully paid` if you wish to settle the invoice or bill with a difference in the amount." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "See the reconcile option" +msgid "Partial payment of an invoice or bill." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:124 +#: ../../content/applications/finance/accounting/payments.rst:136 msgid "Reconciling payments with bank statements" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:126 -msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is to reconcile it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." +#: ../../content/applications/finance/accounting/payments.rst:138 +msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is :doc:`reconciling ` it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." msgstr "" #: ../../content/applications/finance/accounting/payments/batch.rst:3 @@ -5775,11 +6031,11 @@ msgstr "" msgid "Registering a customer payment as part of a batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:32 +#: ../../content/applications/finance/accounting/payments/batch.rst:31 msgid "Add payments to a batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:34 +#: ../../content/applications/finance/accounting/payments/batch.rst:33 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`." msgstr "" @@ -5787,7 +6043,7 @@ msgstr "" msgid "Filling out a new inbound batch payment form" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:42 +#: ../../content/applications/finance/accounting/payments/batch.rst:40 msgid "Click :guilabel:`Add a line`. In the pop-up window, tick all payments to include in the batch deposit, then click :guilabel:`Select`." msgstr "" @@ -5795,15 +6051,15 @@ msgstr "" msgid "Selecting all payments to include in the batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:49 +#: ../../content/applications/finance/accounting/payments/batch.rst:46 msgid "Once done, click :guilabel:`Validate` to finalize the batch deposit." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:52 +#: ../../content/applications/finance/accounting/payments/batch.rst:49 msgid "Click :guilabel:`Print` to download a PDF file to include with the deposit slip." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:57 +#: ../../content/applications/finance/accounting/payments/batch.rst:54 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." msgstr "" @@ -5811,11 +6067,11 @@ msgstr "" msgid "Reconciling the batch payment with all its transactions" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:67 +#: ../../content/applications/finance/accounting/payments/batch.rst:63 msgid "If a specific payment could not be processed by the bank or is missing, remove the related payment before reconciling." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:72 +#: ../../content/applications/finance/accounting/payments/batch.rst:68 msgid ":doc:`batch_sdd`" msgstr "" @@ -6306,198 +6562,72 @@ msgid "Internal transfers" msgstr "" #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:5 -msgid "In Odoo, internal money transfers can be made in a few clicks. You need at least either two bank accounts, two cash journals, or one bank account and one cash journal." +msgid "Internal money transfers can be handled in Odoo. At least two bank accounts are needed to make internal transfers." msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:11 -msgid "An internal transfer account is automatically created on your database based on your company's localization and depending on your country’s legislation. If needed, the default :guilabel:`Internal transfer account` can be modified by going to :menuselection:`Accounting app --> Configuration --> Settings` and then under the :guilabel:`Default Accounts` section." +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 +msgid ":doc:`How to add an additional bank account <../bank>`" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:17 -msgid "At least two bank accounts are needed to make internal transfers. Refer to :doc:`Bank and cash accounts section <../bank>` to see how to add an additional bank account to your database." +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:14 +msgid "An internal transfer account is automatically created on your database based on your company's localization and depending on your country’s legislation. To modify the default :guilabel:`Internal transfer account`, go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down to the :guilabel:`Default Accounts` section." msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:22 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:20 msgid "Register an internal transfer from one bank to another" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:24 -msgid "Let's say you have two bank accounts registered on your database and you want to transfer 1,000 USD from Bank A to Bank B." +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:22 +msgid "If you want to transfer money from one bank to another, access the Accounting Dashboard, click the drop-down selection button (:guilabel:`⋮`) on the bank from which you want to make the transfer, then click :guilabel:`Payments`. Select or create a payment, tick the :guilabel:`Internal Transfer` checkbox, and select a :guilabel:`Destination Journal` before you :guilabel:`Confirm` the internal transfer." msgstr "" #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:28 -msgid "Log an internal transfer" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:30 -msgid "From the Accounting Dashboard, click on the drop-down selection button (:guilabel:`⋮`) on one of your banks. In the :guilabel:`New` column click on :guilabel:`Internal Transfer` and enter the information related to the transfer." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:-1 -msgid "Fill in the information related to your internal transfer" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 -msgid "Fill in the :guilabel:`Memo` field for automatic reconciliation." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 -msgid ":guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer. The money is now booked in the transfer account and another payment is **automatically** created in the destination journal (Bank B)." +msgid "The money is now booked in the transfer account and another payment is automatically created in the destination journal." msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:46 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:33 msgid "Bank journal (Bank A)" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:55 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:42 msgid "Outstanding Payments account" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:73 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:123 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:144 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:44 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:60 msgid "$1,000" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:75 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:45 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:62 msgid "**Internal transfer account**" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:59 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:77 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:127 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:146 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:46 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:64 msgid "**$1,000**" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:63 -msgid "Automated booking - Bank journal (BANK B)" +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:49 +msgid "Bank journal (Bank B)" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:72 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:59 msgid "Outstanding Receipts account" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:80 -msgid "There are one outstanding payment and one outstanding receipt pending in your two bank account journals, because the bank statement confirming the sending and receiving of the money has not been booked yet." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:-1 -msgid "Outstanding Payments/Receipts pending bank statement booking" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:91 -msgid "Manage and reconcile bank statements" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:93 -msgid "The next step is to book the bank statements to finalize the transaction by creating, :doc:`importing <../bank/transactions>`, or :doc:`synchronizing <../bank/bank_synchronization>` your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the :guilabel:`Reconcile` button." +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:66 +msgid "There is **one outstanding payment** and **one outstanding receipt** pending in your two bank account journals because the bank statement confirming the sending and receiving of the money has not been booked yet." msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:-1 -msgid "Transaction lines to be filled in prior to reconciliation" +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 +msgid "Once this is done, you can book and reconcile your bank statement lines as usual." msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:103 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:73 msgid ":doc:`../bank/reconciliation`" msgstr "" -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:105 -msgid "In the next window, choose counterparts for the payment - in this example, the outstanding payment account - then click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:-1 -msgid "Reconcile your payment" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:113 -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:133 -msgid "Bank journal entry" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:122 -msgid "Outstanding Payment" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:125 -msgid "Bank Account (BANK A)" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:129 -msgid "The same steps must be repeated once you receive the bank statement related to Bank B. Book and reconcile your bank statement lines." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:142 -msgid "Outstanding Receipt" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:145 -msgid "Bank Account (BANK B)" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:3 -msgid "Pay several bills at once" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:5 -msgid "Odoo offers the possibility of grouping multiple bills' payments into one, facilitating the reconciliation process." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:9 -#: ../../content/applications/finance/accounting/vendor_bills.rst:13 -msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:10 -msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:13 -msgid "Group payments" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:15 -msgid "To register the payment of multiple bills at once, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, select the bills you wish to register a payment for by **ticking** the boxes next to the bills. When done, either click :guilabel:`Register Payment` or :menuselection:`Action --> Register Payment`." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:-1 -msgid "Register payment button." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:25 -msgid "Payments can only be registered for :guilabel:`posted` bills." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:27 -msgid "When registering the payments, a **pop-up window** appears. From here, you can either create **separate payments** for each bill all at once by clicking :guilabel:`Create Payment`, *or* create one payment by combining **all** bills' payments. To **combine** all payments, tick the :guilabel:`Group Payments` box." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:33 -msgid "The :guilabel:`Group Payments` option only appears when selecting two or more bills." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:-1 -msgid "Group payments options when registering a payment." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:39 -msgid "When selecting :guilabel:`Group Payments`, the :guilabel:`amount, currency, date and memo` are all set automatically, but you can modify them according to your needs." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:43 -msgid "Partial group payments with cash discounts" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:45 -msgid "In case of **partial group payments with cash discounts**, you can follow the steps found on the :doc:`cash discount documentation page `. Make sure to apply the :doc:`payment terms ` to the **bills** *instead* of the invoices." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:53 -msgid ":doc:`/applications/finance/accounting/customer_invoices/payment_terms`" -msgstr "" - #: ../../content/applications/finance/accounting/payments/online.rst:5 msgid "Online payments" msgstr "" @@ -6619,74 +6749,78 @@ msgid "Activate checks payment methods" msgstr "" #: ../../content/applications/finance/accounting/payments/pay_checks.rst:15 -msgid "To activate the checks payment method, go to :menuselection:`Accounting --> Configuration --> Checks`, there you can activate the payment method as well as set up the :guilabel:`Check Layout`. Once activated the :guilabel:`Checks` setting, the feature is automatically setup for your :guilabel:`Outgoing Payments`." +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`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:20 +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." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:21 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:22 msgid "Some countries require specific modules to print checks; such modules may be installed by default. For instance, the :guilabel:`U.S. Checks Layout` module is required to print U.S. checks." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:26 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:27 msgid "Compatible check stationery for printing checks" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:29 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:30 msgid "United States" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:31 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:32 msgid "For the United States, Odoo supports by default the check formats of:" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:33 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom;" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 msgid "**Peachtree**: check in the middle, stubs on top and bottom;" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:36 msgid "**ADP**: check in the bottom, and stubs on the top." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:38 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:39 msgid "Pay a supplier bill with a check" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:40 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:41 msgid "Paying a supplier with a check is done in three steps:" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:42 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 msgid "registering a payment" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 msgid "printing checks in batch for all registered payments" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:45 msgid "reconciling bank statements" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:47 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:48 msgid "Register a payment by check" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:49 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:50 msgid "To register a payment, open any supplier bill from the menu :menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is validated, you can register a payment. Set the :guilabel:`Payment Method` to :guilabel:`Checks` and validate the payment." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:55 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:56 msgid "Print checks" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:57 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:58 msgid "On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, you can see the number of checks registered. By clicking on :guilabel:`Checks to print` you have got the possibility to print the reconciled checks." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:61 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:62 msgid "To print all checks in batch, select all payments from the list view and click on :guilabel:`Print`." msgstr "" @@ -8276,6 +8410,11 @@ msgstr "" msgid "You can find additional information about VAT and its mechanism on this page from the European Commission: `\"What is VAT?\" `_." msgstr "" +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 +msgid "Prerequisites" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:25 msgid "Tax Return Periodicity" msgstr "" @@ -8371,7 +8510,7 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:117 -#: ../../content/applications/finance/accounting/taxes/retention.rst:70 +#: ../../content/applications/finance/accounting/taxes/retention.rst:42 msgid ":doc:`../taxes`" msgstr "" @@ -8544,7 +8683,7 @@ msgid "There are numerous types of **taxes**, and their application varies great msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:16 -msgid "**Default Taxes** define which taxes are automatically selected when creating a new product. They are also used to prefill the :guilabel:`Taxes` field when adding a new line on an invoice in **Accounting Firms** mode." +msgid "**Default taxes** define which taxes are automatically selected when creating a new product. They are also used to prefill the :guilabel:`Taxes` field when adding a new line on an invoice in :ref:`Accounting Firms ` mode." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 @@ -8552,7 +8691,7 @@ msgid "Odoo fills out the Tax field automatically according to the Default Taxes msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:23 -msgid "To change your **Default Taxes**, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Default Taxes`, select the appropriate taxes for your default **Sales Tax** and **Purchase Tax**, and click on *Save*." +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 :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 @@ -8560,359 +8699,372 @@ msgid "Define which taxes to use by default on Odoo" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:31 -msgid "**Default Taxes** are automatically set up according to the country selected at the creation of your database, or when you set up a :ref:`fiscal localization package ` for your company." +msgid "**Default taxes** are automatically set up according to the country selected at the creation of your database, or when you set up a :ref:`fiscal localization package ` for your company." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:38 -msgid "Activate Sales Taxes from the List view" +msgid "Activate sales taxes from the list view" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:40 -msgid "As part of your :ref:`fiscal localization package `, most of your country's sales taxes are already preconfigured on your database. However, only a few of them are activated by default, so that you can activate only the ones relevant for your business." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:44 -msgid "To activate Sale Taxes, go to :menuselection:`Accounting --> Configuration --> Taxes` and use the *Activate* toggle button to activate or deactivate a tax." +msgid "As part of your :ref:`fiscal localization package `, most of your country's sales taxes are already preconfigured on your database. However, only a few taxes are activated by default. To activate taxes relevant to your business, go to :menuselection:`Accounting --> Configuration --> Taxes` and enable the toggle button under the :guilabel:`Active` column." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 msgid "Activate pre-configured taxes in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:55 -msgid "To edit or create a **Tax**, go to :menuselection:`Accounting --> Configuration --> Taxes` and open a tax or click on *Create*." +#: ../../content/applications/finance/accounting/taxes.rst:53 +msgid "To edit or create a **tax**, go to :menuselection:`Accounting --> Configuration --> Taxes` and open a tax or click on :guilabel:`New`." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 msgid "Edition of a tax in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:64 -msgid "Taxes have three different labels, each one having a specific use. Refer to the following table to see where they are displayed." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:68 -msgid ":ref:`Tax Name `" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:68 -msgid ":ref:`Label on Invoice `" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:68 -msgid ":ref:`Tax Group `" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:71 -msgid "Back end" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:71 -msgid "*Taxes* column on exported invoices" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:71 -msgid "Above the *Total* line on exported invoices" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:76 -msgid "Basic Options" +#: ../../content/applications/finance/accounting/taxes.rst:60 +msgid "Basic options" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:81 -msgid "Tax Name" +#: ../../content/applications/finance/accounting/taxes.rst:65 +msgid "Tax name" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:83 -msgid "The **Tax Name** as you want to display it for backend users. This is the :ref:`label ` you see while editing Sales Orders, Invoices, Products, etc." +#: ../../content/applications/finance/accounting/taxes.rst:67 +msgid "The **tax name** is displayed for backend users in the :guilabel:`Taxes` field in :doc:`sales orders <../../sales/sales>`, :doc:`invoices `, product forms, etc." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:89 -msgid "Tax Computation" +#: ../../content/applications/finance/accounting/taxes.rst:73 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:306 +msgid "Tax computation" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:91 +#: ../../content/applications/finance/accounting/taxes.rst:75 msgid "**Group of Taxes**" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:93 -msgid "The tax is a combination of multiple sub-taxes. You can add as many taxes you want, in the order you want them to be applied." +#: ../../content/applications/finance/accounting/taxes.rst:77 +msgid "The tax is a combination of multiple sub-taxes. You can add as many taxes as you want, in the order you want them to be applied." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:97 +#: ../../content/applications/finance/accounting/taxes.rst:81 msgid "Make sure that the tax sequence is correct, as the order in which they are may impact the taxes' amounts computation, especially if one of the taxes :ref:`affects the base of the subsequent ones `." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:101 +#: ../../content/applications/finance/accounting/taxes.rst:85 msgid "**Fixed**" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:103 -msgid "The tax has a fixed amount in the default currency. The amount remains the same, regardless of the Sales Price." +#: ../../content/applications/finance/accounting/taxes.rst:87 +msgid "The tax has a fixed amount in the default currency. The amount remains the same, regardless of the sales price." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:106 -msgid "For example, a product has a Sales Price of $1000, and we apply a *$10 fixed* tax. We then have:" +#: ../../content/applications/finance/accounting/taxes.rst:91 +msgid "A product has a sales price of $1000, and we apply a $10 *fixed* tax. We then have:" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:94 #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 -#: ../../content/applications/finance/accounting/taxes.rst:138 -#: ../../content/applications/finance/accounting/taxes.rst:251 -msgid "Product's Sales Price" +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Product sales price" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:94 #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 -#: ../../content/applications/finance/accounting/taxes.rst:138 -#: ../../content/applications/finance/accounting/taxes.rst:251 +#: ../../content/applications/finance/accounting/taxes.rst:268 msgid "Price without tax" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:94 #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 -#: ../../content/applications/finance/accounting/taxes.rst:138 -#: ../../content/applications/finance/accounting/taxes.rst:251 +#: ../../content/applications/finance/accounting/taxes.rst:268 #: ../../content/applications/finance/fiscal_localizations/romania.rst:92 msgid "Tax" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:94 #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 -#: ../../content/applications/finance/accounting/taxes.rst:138 -#: ../../content/applications/finance/accounting/taxes.rst:251 +#: ../../content/applications/finance/accounting/taxes.rst:268 msgid "Total" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:97 #: ../../content/applications/finance/accounting/taxes.rst:112 #: ../../content/applications/finance/accounting/taxes.rst:127 -#: ../../content/applications/finance/accounting/taxes.rst:141 -#: ../../content/applications/finance/accounting/taxes.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:271 msgid "1,000" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:97 #: ../../content/applications/finance/fiscal_localizations/france.rst:84 msgid "10" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:97 msgid "1,010.00" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:115 -msgid "**Percentage of Price**" +#: ../../content/applications/finance/accounting/taxes.rst:100 +msgid "**Percentage of price**" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:117 -msgid "The *Sales Price* is the taxable basis: the tax's amount is computed by multiplying the Sales Price by the tax's percentage." +#: ../../content/applications/finance/accounting/taxes.rst:102 +msgid "The *sales price* is the taxable basis: the tax amount is computed by multiplying the sales price by the tax percentage." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:120 -msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price* tax. We then have:" +#: ../../content/applications/finance/accounting/taxes.rst:106 +msgid "A product has a sales price of $1000, and we apply a *10% of Price* tax. We then have:" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:127 +#: ../../content/applications/finance/accounting/taxes.rst:112 msgid "1,100.00" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:130 +#: ../../content/applications/finance/accounting/taxes.rst:115 msgid "**Percentage of Price Tax Included**" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:132 -msgid "The *Total* is the taxable basis: the tax's amount is a percentage of the Total." +#: ../../content/applications/finance/accounting/taxes.rst:117 +msgid "The **total** is the taxable basis: the tax amount is a percentage of the total." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:134 -msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price Tax Included* tax. We then have:" +#: ../../content/applications/finance/accounting/taxes.rst:120 +msgid "A product has a Sales Price of $1000, and we apply a *10% of Price Tax Included* tax. We then have:" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:141 +#: ../../content/applications/finance/accounting/taxes.rst:127 msgid "111.11" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:141 +#: ../../content/applications/finance/accounting/taxes.rst:127 msgid "1,111.11" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:147 +#: ../../content/applications/finance/accounting/taxes.rst:130 +msgid "**Python code**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:132 +msgid "A tax defined as **Python code** consists of two snippets of Python code that are executed in a local environment containing data such as the unit price, product or partner. :guilabel:`Python Code` defines the amount of the tax, and :guilabel:`Applicable Code` defines if the tax is to be applied. The formula is found at the bottom of the :guilabel:`Definition` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:138 +msgid ":guilabel:`Python Code`: `result = price_unit * 0.10` :guilabel:`Applicable Code`: `result = true`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:144 msgid "Active" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:149 -msgid "Only **Active** taxes can be added to new documents." +#: ../../content/applications/finance/accounting/taxes.rst:146 +msgid "Only **active** taxes can be added to new documents." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:152 +#: ../../content/applications/finance/accounting/taxes.rst:149 msgid "It is not possible to delete taxes that have already been used. Instead, you can deactivate them to prevent future use." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:156 -msgid "This field can be modified from the *List View*. See :ref:`above ` for more information." +#: ../../content/applications/finance/accounting/taxes.rst:153 +msgid "This field can be modified from the :ref:`list view `." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:162 -msgid "Tax Scope" +#: ../../content/applications/finance/accounting/taxes.rst:158 +msgid "Tax type" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:164 -msgid "The **Tax Scope** determines the tax's application, which also restricts where it is displayed." +#: ../../content/applications/finance/accounting/taxes.rst:160 +msgid "The :guilabel:`Tax Type` determines the tax application, which also restricts where it is displayed." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:166 -msgid "**Sales**: Customer Invoices, Product's Customer Taxes, etc." +#: ../../content/applications/finance/accounting/taxes.rst:162 +msgid "**Sales**: Customer invoices, product customer taxes, etc." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:167 -msgid "**Purchase**: Vendor Bills, Product's Vendor Taxes, etc." +#: ../../content/applications/finance/accounting/taxes.rst:163 +msgid "**Purchase**: Vendor bills, product vendor taxes, etc." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:168 +#: ../../content/applications/finance/accounting/taxes.rst:164 msgid "**None**" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:167 +msgid "You can use :guilabel:`None` for taxes that you want to include in a :ref:`Group of Taxes ` but that you do not want to list along with other sales or purchase taxes." +msgstr "" + #: ../../content/applications/finance/accounting/taxes.rst:171 -msgid "You can use **None** for taxes that you want to include in a :ref:`Group of Taxes ` but that you don't want to list along with other Sales or Purchase taxes." +msgid "Tax scope" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:177 -msgid "Definition tab" +#: ../../content/applications/finance/accounting/taxes.rst:173 +msgid "The :guilabel:`Tax Scope` restricts the use of taxes to a type of product, either **goods** or **services**." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:179 -msgid "Allocate with precision the amount of the taxable basis or percentages of the computed tax to multiple accounts and Tax Grids." +msgid "Definition tab" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:-1 -msgid "Allocate tax amounts to the right accounts and tax grids" +#: ../../content/applications/finance/accounting/taxes.rst:181 +msgid "Allocate with precision the amount of the taxable basis or percentages of the computed tax to multiple accounts and tax grids." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:185 -msgid "**Based On**:" +#: ../../content/applications/finance/accounting/taxes.rst:-1 +msgid "Allocate tax amounts to the right accounts and tax grids" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:187 -msgid "Base: the price on the invoice line" +msgid "**Based On**:" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:188 -msgid "% of tax: a percentage of the computed tax." +#: ../../content/applications/finance/accounting/taxes.rst:189 +msgid ":guilabel:`Base`: the price on the invoice line" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:190 -msgid "**Account**: if defined, an additional Journal Item is recorded." +msgid ":guilabel:`% of tax`: a percentage of the computed tax." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:191 -msgid "**Tax Grids**: used to generate :doc:`Tax Reports ` automatically, according to your country's regulations." +#: ../../content/applications/finance/accounting/taxes.rst:192 +msgid "**Account**: if defined, an additional journal item is recorded." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:197 -msgid "Advanced Options tab" +#: ../../content/applications/finance/accounting/taxes.rst:193 +msgid "**Tax Grids**: used to generate :doc:`tax reports ` automatically, according to your country's regulations." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:202 -msgid "Label on Invoices" +#: ../../content/applications/finance/accounting/taxes.rst:199 +msgid "Advanced options tab" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:204 -msgid "The label of the tax, as displayed on each invoice line in the **Taxes** column. This is the :ref:`label ` visible to *front end* users, on exported invoices, on their Customer Portals, etc." +msgid "Label on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:206 +msgid "The tax label is displayed on each invoice line in the :guilabel:`Taxes` column. This is visible to *front-end* users on exported invoices, in customer portals, etc." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 -msgid "The Label on Invoices is displayed on each invoice line" +msgid "The label on invoices is displayed on each invoice line" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:214 -msgid "Tax Group" +#: ../../content/applications/finance/accounting/taxes.rst:215 +msgid "Tax group" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:216 -msgid "Select to which **Tax Group** the tax belongs. The Tax Group name is the :ref:`label ` displayed above the *Total* line on exported invoices, and the Customer Portals." +#: ../../content/applications/finance/accounting/taxes.rst:217 +msgid "Select which **tax group** the tax belongs to. The tax group name is the displayed above the **total** line on exported invoices and in customer portals." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:219 -msgid "Tax groups include different iterations of the same tax. This can be useful when you must record differently the same tax according to :doc:`Fiscal Positions `." +#: ../../content/applications/finance/accounting/taxes.rst:220 +msgid "Tax groups include different iterations of the same tax. This can be useful when you must record the same tax differently according to :doc:`fiscal positions `." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 msgid "The Tax Group name is different from the Label on Invoices" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:225 -msgid "In the example above, we see a 0% tax for Intra-Community customers in Europe. It records amounts on specific accounts and with specific tax grids. Still, to the customer, it is a 0% tax. That's why the :ref:`Label on the Invoice ` indicates *0% EU*, and the Tax Group name, above the *Total* line, indicates *0%*." +#: ../../content/applications/finance/accounting/taxes.rst:228 +msgid "In the example above, the :guilabel:`0% EU S` tax for intra-community customers in Europe records the amount on specific accounts and tax grids. However, it remains a 0% tax to the customer. This is why the label indicates :guilabel:`0% EU S`, and the tax group name above the :guilabel:`Total` line indicates :guilabel:`VAT 0%`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:234 +msgid "Taxes have three different labels, each one having a specific use. Refer to the following table to see where they are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Name `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Label on Invoice `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Group `" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:233 -msgid "Include in Analytic Cost" +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Backend" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:235 -msgid "With this option activated, the tax's amount is assigned to the same **Analytic Account** as the invoice line." +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid ":guilabel:`Taxes` column on exported invoices" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:241 -msgid "Included in Price" +msgid "Above the :guilabel:`Total` line on exported invoices" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:243 -msgid "With this option activated, the total (including the tax) equals the **Sales Price**." +#: ../../content/applications/finance/accounting/taxes.rst:249 +msgid "Include in analytic cost" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:245 -msgid ":dfn:`Total = Sales Price = Computed Tax-Excluded price + Tax`" +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "With this option activated, the tax amount is assigned to the same **analytic account** as the invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:257 +msgid "Included in price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:259 +msgid "With this option activated, the total (including the tax) equals the **sales price**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:261 +msgid "`Total = Sales Price = Computed Tax-Excluded price + Tax`" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:247 -msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price* tax, which is *included in the price*. We then have:" +#: ../../content/applications/finance/accounting/taxes.rst:264 +msgid "A product has a sales price of $1000, and we apply a *10% of Price* tax, which is *included in the price*. We then have:" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:271 msgid "900.10" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:271 msgid "90.9" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:271 msgid "1,000.00" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:258 +#: ../../content/applications/finance/accounting/taxes.rst:275 msgid "If you need to define prices accurately, both tax-included and tax-excluded, please refer to the following documentation: :doc:`taxes/B2B_B2C`." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:262 -msgid "**Invoices**: By default, the Line Subtotals displayed on your invoices are *Tax-Excluded*. To display *Tax-Included* Line Subtotals, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices`, and select *Tax-Included* in the **Line Subtotals Tax Display** field, then click on *Save*." +#: ../../content/applications/finance/accounting/taxes.rst:279 +msgid "By default, only the :guilabel:`Tax excluded` column is displayed on invoices. To display the :guilabel:`Tax included` column, click the **dropdown toggle** button and check :guilabel:`Tax incl.`." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:266 -msgid "**eCommerce**: By default, the prices displayed on your eCommerce website are *Tax-Excluded*. To display *Tax-Included* prices, go to :menuselection:`Website --> Configuration --> Settings --> Pricing`, and select *Tax-Included* in the **Product Prices** field, then click on *Save*." +#: ../../content/applications/finance/accounting/taxes.rst:288 +msgid "Affect base of subsequent taxes" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:273 -msgid "Affect Base of Subsequent Taxes" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:275 +#: ../../content/applications/finance/accounting/taxes.rst:290 msgid "With this option, the total tax-included becomes the taxable basis for the other taxes applied to the same product." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:278 -msgid "You can configure a new :ref:`Group of Taxes ` to include this tax, or add it directly to a product line." +#: ../../content/applications/finance/accounting/taxes.rst:293 +msgid "You can configure a new :ref:`group of taxes ` to include this tax or add it directly to a product line." msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:-1 msgid "The eco-tax is taken into the basis of the 21% VAT tax" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:285 +#: ../../content/applications/finance/accounting/taxes.rst:300 msgid "The order in which you add the taxes on a product line has no effect on how amounts are computed. If you add taxes directly on a product line, only the tax sequence determines the order in which they are applied." msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:289 +#: ../../content/applications/finance/accounting/taxes.rst:304 msgid "To reorder the sequence, go to :menuselection:`Accounting --> Configuration --> Taxes`, and drag and drop the lines with the handles next to the tax names." msgstr "" @@ -8920,15 +9072,19 @@ msgstr "" msgid "The taxes' sequence in Odoo determines which tax is applied first" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:297 +#: ../../content/applications/finance/accounting/taxes.rst:311 msgid ":doc:`taxes/fiscal_positions`" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:298 +#: ../../content/applications/finance/accounting/taxes.rst:312 msgid ":doc:`taxes/B2B_B2C`" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:299 +#: ../../content/applications/finance/accounting/taxes.rst:313 +msgid ":doc:`taxes/taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:314 msgid ":doc:`reporting/tax_returns`" msgstr "" @@ -8989,6 +9145,7 @@ msgid "In terms of finance, you have no more revenues selling your product at 10 msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:413 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:10 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:6 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 @@ -9515,51 +9672,39 @@ msgid "Withholding taxes" msgstr "" #: ../../content/applications/finance/accounting/taxes/retention.rst:5 -msgid "A withholding tax, also called a retention tax, is a government requirement for the payer of a customer invoice to withhold or deduct tax from the payment, and pay that tax to the government. In most jurisdictions, withholding tax applies to employment income." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/retention.rst:10 -msgid "With normal taxes, the tax is added to the subtotal to give you the total to pay. As opposed to normal taxes, withholding taxes are deducted from the amount to pay, as the tax will be paid by the customer." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/retention.rst:14 -msgid "As, an example, in Colombia you may have the following invoice:" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/retention.rst:19 -msgid "In this example, the **company** who sent the invoice owes $20 of taxes to the **government** and the **customer** owes $10 of taxes to the **government**." +msgid "A **withholding tax**, also known as retention tax, mandates the payer of a customer invoice to deduct a tax from the payment and remit it to the government. Typically, a tax is included in the subtotal to calculate the total amount paid, while withholding taxes are directly subtracted from the payment." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:25 -msgid "In Odoo, a withholding tax is defined by creating a negative tax. For a retention of 10%, you would configure the following tax (accessible through :menuselection:`Configuration --> Taxes`):" +#: ../../content/applications/finance/accounting/taxes/retention.rst:13 +msgid "In Odoo, a withholding tax is defined by creating a negative tax. To create one, go to :menuselection:`Accounting --> Configuration --> Taxes` and, in the :guilabel:`Amount` field, enter a negative amount." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:32 -msgid "In order to make it appear as a retention on the invoice, you should set a specific tax group **Retention** on your tax, in the **Advanced Options** tab." +#: ../../content/applications/finance/accounting/taxes/retention.rst:-1 +msgid "negative tax amount in field" msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:39 -msgid "Once the tax is defined, you can use it in your products, sales order or invoices." +#: ../../content/applications/finance/accounting/taxes/retention.rst:20 +msgid "Then, go to the :menuselection:`Advanced Options` tab and create a retention :guilabel:`Tax Group`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:43 -msgid "If the retention is a percentage of a regular tax, create a Tax with a **Tax Computation** as a **Tax Group** and set the two taxes in this group (normal tax and retention)." +#: ../../content/applications/finance/accounting/taxes/retention.rst:-1 +msgid "tax group for retention tax." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:48 -msgid "Applying retention taxes on invoices" +#: ../../content/applications/finance/accounting/taxes/retention.rst:26 +msgid "If the retention is a percentage of a regular tax, create a :guilabel:`Tax` with a :guilabel:`Tax Computation` as a :guilabel:`Group of Taxes`. Then, set both the regular tax and the retention one in the :guilabel:`Definition` tab." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:50 -msgid "Once your tax is created, you can use it on customer forms, sales order or customer invoices. You can apply several taxes on a single customer invoice line." +#: ../../content/applications/finance/accounting/taxes/retention.rst:31 +msgid "Retention taxes on invoices" msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:58 -msgid "When you see the customer invoice on the screen, you get only a **Taxes line** summarizing all the taxes (normal taxes & retentions). But when you print or send the invoice, Odoo does the correct grouping amongst all the taxes." +#: ../../content/applications/finance/accounting/taxes/retention.rst:33 +msgid "Once the retention tax has been created, it can be used on customer forms, sales orders, and customer invoices. Several taxes can be applied on a single customer invoice line." msgstr "" -#: ../../content/applications/finance/accounting/taxes/retention.rst:63 -msgid "The printed invoice will show the different amounts in each tax group." +#: ../../content/applications/finance/accounting/taxes/retention.rst:-1 +msgid "invoice lines with taxes" msgstr "" #: ../../content/applications/finance/accounting/taxes/taxcloud.rst:3 @@ -9567,10 +9712,14 @@ msgid "TaxCloud integration" msgstr "" #: ../../content/applications/finance/accounting/taxes/taxcloud.rst:6 -msgid "The Odoo TaxCloud integration has begun its decommissioning, starting in Odoo 17. New installations are prohibited in Odoo 17, and in Odoo 18, the TaxCloud module(s) won't exist at all. Odoo recommends the use of the Avatax platform." +msgid "The out-of-the-box Odoo TaxCloud integration has begun its decommissioning. Starting in Odoo 17, new installations are prohibited, and in Odoo 18 the TaxCloud module(s) won't exist at all. Odoo recommends the use of the Avatax platform." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:10 +msgid "If you are hosted on-premise or on Odoo.SH and you wish to use Taxcloud, you can contact them directly `here `_." msgstr "" -#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:11 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:14 msgid ":doc:`avatax`" msgstr "" @@ -9617,7 +9766,7 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:704 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 #: ../../content/applications/finance/fiscal_localizations/italy.rst:279 msgid "Vendor bills" msgstr "" @@ -9630,6 +9779,10 @@ msgstr "" msgid "Tutorial `Registering a vendor bill `_" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills.rst:13 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills.rst:16 msgid "Bill creation" msgstr "" @@ -9790,6 +9943,10 @@ msgstr "" msgid "Declining Then Straight Line" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 +msgid "The server checks once a day if an entry must be posted. It might then take up to 24 hours before you see a change from *draft* to *posted*." +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:34 msgid "Such transactions must be posted on an **Assets Account** rather than on the default expense account." msgstr "" @@ -9798,6 +9955,10 @@ msgstr "" msgid "Configure an Assets Account" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 +msgid "To configure your account in the **Chart of Accounts**, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:-1 msgid "Configuration of an Assets Account in Odoo Accounting" msgstr "" @@ -9807,12 +9968,10 @@ msgid "This account's type must be either *Fixed Assets* or *Non-current Assets* msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:51 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:48 msgid "Post an expense to the right account" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:54 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:51 msgid "Select the account on a draft bill" msgstr "" @@ -9825,12 +9984,10 @@ msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:65 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:61 msgid "Choose a different Expense Account for specific products" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:67 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 msgid "Start editing the product, go to the *Accounting* tab, select the right **Expense Account**, and save." msgstr "" @@ -9842,15 +9999,26 @@ msgstr "" msgid "It is possible to :ref:`automate the creation of assets entries ` for these products." msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 +msgid "Change the account of a posted journal item" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:83 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:77 msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, select the journal item you want to modify, click on the account, and select the right one." msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:-1 +msgid "Modification of a posted journal item's account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:92 msgid "Assets entries" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 +msgid "Create a new entry" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:99 msgid "An **Asset entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time." msgstr "" @@ -9875,6 +10043,10 @@ msgstr "" msgid "Depreciation Board in Odoo Accounting" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 +msgid "What does \"Prorata Temporis\" mean?" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:124 msgid "The **Prorata Temporis** feature is useful to depreciate your assets the most accurately possible." msgstr "" @@ -9995,6 +10167,10 @@ msgstr "" msgid "When you create a new Asset entry, fill out the **Fixed Asset Account** with the right asset account." msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 +msgid "New buttons with all the models linked to that account appear at the top of the form. Clicking on a model button fills out the form according to that model." +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:-1 msgid "Assets model button in Odoo Accounting" msgstr "" @@ -10011,6 +10187,10 @@ msgstr "" msgid "You have three choices for the **Automate Assets** field:" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:241 msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Assets entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Assets`." msgstr "" @@ -10027,168 +10207,122 @@ msgstr "" msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: :ref:`product-assets-account`)." msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 +msgid ":doc:`../get_started/chart_of_accounts`" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:3 -msgid "Deferred expenses and prepayments" +msgid "Deferred expenses" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:5 -msgid "**Deferred expenses** and **prepayments** (also known as **prepaid expense**), are both costs that have already occurred for unconsumed products or services yet to receive." +msgid "**Deferred expenses** and **prepayments** (also known as **prepaid expenses**) are both costs that have already occurred for products or services yet to be received." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:8 -msgid "Such costs are **assets** for the company that pays them since it already paid for products and services still to receive or that are yet to be used. The company cannot report them on the current **Profit and Loss statement**, or *Income Statement*, since the payments will be effectively expensed in the future." +msgid "Such costs are **assets** for the company that pays them since it already paid for products and services but has either not yet received them or not yet used them. The company cannot report them on the current **profit and loss statement**, or *income statement*, since the payments will be effectively expensed in the future." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:13 -msgid "These future expenses must be deferred on the company's balance sheet until the moment in time they can be **recognized**, at once or over a defined period, on the Profit and Loss statement." +msgid "These future expenses must be deferred on the company's balance sheet until the moment in time they can be **recognized**, at once or over a defined period, on the profit and loss statement." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:16 -msgid "For example, let's say we pay $ 1200 at once for one year of insurance. We already pay the cost now but haven't used the service yet. Therefore, we post this new expense in a *prepayment account* and decide to recognize it on a monthly basis. Each month, for the next 12 months, $ 100 will be recognized as an expense." +msgid "For example, let's say we pay $1200 at once for one year of insurance. We already pay the cost now but haven't used the service yet. Therefore, we post this new expense in a *prepayment account* and decide to recognize it on a monthly basis. Each month, for the next 12 months, $100 will be recognized as an expense." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:21 -msgid "Odoo Accounting handles deferred expenses and prepayments by spreading them in multiple entries that are automatically created in *draft mode* and then posted periodically." +msgid "Odoo Accounting handles deferred expenses by spreading them across multiple entries that are posted periodically." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:31 -msgid "Such transactions must be posted on a **Deferred Expense Account** rather than on the default expense account." -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:35 -msgid "Configure a Deferred Expense Account" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Configuration of a Deferred Expense Account in Odoo Accounting" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:45 -msgid "This account's type must be either *Current Assets* or *Prepayments*" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:53 -msgid "On a draft bill, select the right account for all the products of which the expenses must be deferred." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:41 +msgid "By default, Odoo :ref:`automatically generates ` the deferral entries when you post a vendor bill. However, you can also choose to :ref:`generate them manually ` by selecting the :guilabel:`Manually & Grouped` option instead." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Selection of a Deferred Expense Account on a draft bill in Odoo Accounting" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:46 +msgid "Suppose a bill of $1200 must be deferred over 12 months. The :guilabel:`Equal per month` computation recognizes $100 each month, while the :guilabel:`Based on days` computation recognizes different amounts depending on the number of days in each month." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Change of the Expense Account for a product in Odoo" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:56 +msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Bill Date`." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:71 -msgid "It is possible to automate the creation of expense entries for these products (see: `Automate the Deferred Expenses`_)." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:60 +msgid "For each line of the bill that should be deferred, specify the start and end dates of the deferral period." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:86 -msgid "Deferred Expenses entries" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 +msgid "If the :guilabel:`Generate Entries` field is set to :guilabel:`On invoice/bill validation`, Odoo automatically generates the deferral entries when the bill is validated. Click on the :guilabel:`Deferred Entries` smart button to see them." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:91 -msgid "A **Deferred Expense entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time until the full amount of the expense is recognized." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:67 +msgid "One entry, dated on the same day as the bill, moves the bill amounts from the expense account to the deferred account. The other entries are deferral entries which will, month after month, move the bill amounts from the deferred account to the expense account to recognize the expense." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:94 -msgid "To create a new entry, go to :menuselection:`Accounting --> Accounting --> Deferred Expense`, click on *Create*, and fill out the form." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:72 +msgid "You can defer a January bill of $1200 over 12 months by specifying a start date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800 is recognized as an expense, whereas $400 remains on the deferred account." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 -msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Expenses** tab." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:79 +msgid "The deferred expense report computes an overview of the necessary deferral entries for each account. To access it, go to :menuselection:`Accounting --> Reporting --> Deferred Expense`." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Deferred Expense entry in Odoo Accounting" +msgid "Deferred expense report" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:105 -msgid "Once done, you can click on *Compute Deferral* (next to the *Confirm* button) to generate all the values of the **Expense Board**. This board shows you all the entries that Odoo will post to recognize your expense, and at which date." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:89 +msgid "Only bills whose accounting date is before the end of the period of the report are taken into account." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Expense Board in Odoo Accounting" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:102 +msgid "At the end of each month, go to the Deferred Expenses report and click the :guilabel:`Generate Entries` button. This generates two deferral entries:" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 -msgid "The **Prorata Temporis** feature is useful to recognize your expense the most accurately possible." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:105 +msgid "One dated at the end of the month which aggregates, for each account, all the deferred amounts of that month. This means that at the end of that period, a part of the deferred expense is recognized." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:118 -msgid "With this feature, the first entry on the Expense Board is computed based on the time left between the *Prorata Date* and the *First Recognition Date* rather than the default amount of time between recognitions." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:113 +msgid "There are two bills:" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:122 -msgid "For example, the Expense Board above has its first expense with an amount of $ 70.97 rather than $ 100.00. Consequently, the last entry is also lower and has an amount of $ 29.03." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:115 +msgid "Bill A: $1200 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 -msgid "Deferred Entry from the Purchases Journal" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 +msgid "Bill B: $600 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:128 -msgid "You can create a deferred entry from a specific journal item in your **Purchases Journal**." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:124 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:141 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 +msgid "Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both bills)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:130 -msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, and select the journal item you want to defer. Make sure that it is posted in the right account (see: `Change the account of a posted journal item`_)." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:125 +msgid "Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of bill A and bill B)" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:142 -msgid "Deferred Expense Models" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:144 -msgid "You can create **Deferred Expense Models** to create your Deferred Expense entries faster." -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 -msgid "To create a model, go to :menuselection:`Accounting --> Configuration --> Deferred Expense Models`, click on *Create*, and fill out the form the same way you would do to create a new entry." -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:150 -msgid "You can also convert a *confirmed Deferred Expense entry* into a model by opening it from :menuselection:`Accounting --> Accounting --> Deferred Expenses` and then, by clicking on the button *Save Model*." +msgid "Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of bill A and bill B)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:155 -msgid "Apply a Deferred Expense Model to a new entry" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 -msgid "When you create a new Deferred Expense entry, fill out the **Deferred Expense Account** with the right recognition account." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:158 +msgid "Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of bill A and bill B)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Deferred Expense model button in Odoo Accounting" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:170 -msgid "Automate the Deferred Expenses" +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:165 +msgid "There is no need to generate entries in December. Indeed, if we do the computation for December, we will have an amount of 0 to be deferred." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 -msgid "When you create or edit an account of which the type is either *Current Assets* or *Prepayments*, you can configure it to defer the expenses that are credited on it automatically." +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:171 +msgid "bill A and bill B" msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 -msgid "You have three choices for the **Automate Deferred Expense** field:" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:178 -msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Deferred Expenses entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Deferred Expenses`." -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:181 -msgid "**Create and validate:** you must also select a Deferred Expense Model (see: `Deferred Expense Models`_). Whenever a transaction is posted on the account, a *Deferred Expenses entry* is created and immediately validated." -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:-1 -msgid "Automate Deferred Expense on an account in Odoo Accounting" -msgstr "" - -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:190 -msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: `Choose a different Expense Account for specific products`_)." +msgid "Therefore, at the end of December, bills A and B are fully recognized as expense only once in spite of all the created entries thanks to the reversal mechanism." msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:3 @@ -10348,8 +10482,8 @@ msgid "Workspaces are hierarchical folders having their own set of tags and :ref msgstr "" #: ../../content/applications/finance/documents.rst:47 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1051 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 msgid ":guilabel:`Name`" @@ -10389,6 +10523,8 @@ msgstr "" #: ../../content/applications/finance/documents.rst:74 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 #: ../../content/applications/finance/fiscal_localizations/austria.rst:16 #: ../../content/applications/finance/fiscal_localizations/chile.rst:32 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 @@ -12027,7 +12163,7 @@ msgid "A list showing less common Argentinean tax options, which are labeled as msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:200 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:256 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:252 msgid "Document types" msgstr "" @@ -12084,7 +12220,7 @@ msgid "document types grouped by letters." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:243 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 msgid "Use on invoices" msgstr "" @@ -12201,7 +12337,7 @@ msgid "When creating :guilabel:`Purchase Journals`, it's possible to define whet msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:395 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:391 #: ../../content/applications/finance/fiscal_localizations/peru.rst:351 msgid "Usage and testing" msgstr "" @@ -13008,382 +13144,1581 @@ msgstr "" msgid "Australia" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:8 -msgid "Employment Hero Australian Payroll" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:14 +msgid "Module Name" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:10 -msgid "The Employment Hero module synchronizes payslip accounting entries (e.g., expenses, social charges, liabilities, taxes) from Employment Hero to Odoo automatically. Payroll administration is still done in Employment Hero. We only record the journal entries in Odoo." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:15 +msgid "Module Key" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:15 -msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:17 +msgid ":guilabel:`Australia - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +msgid "`l10n_au`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:20 -msgid ":ref:`Activate ` the :guilabel:`Employment Hero Australian Payroll` module (technical name: `l10n_au_keypay`)." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:19 +msgid "Installed by default when the Accounting :guilabel:`Fiscal Localization` package is set to :guilabel:`Australia`. This module also installs the :guilabel:`ABA credit transfer` and the :guilabel:`Remittance Advice report` module." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:22 -msgid "Configure the **Employment Hero API** by going to :menuselection:`Accounting --> Configuration --> Settings`. More fields become visible after clicking on :guilabel:`Enable Employment Hero Integration`." +msgid ":guilabel:`Australian Reports - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" -"settings" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:23 +msgid "`l10n_au_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:24 +msgid "Includes the :guilabel:`Taxable Payments Annual Reports (TPAR)` and the :guilabel:`BAS report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:26 +msgid ":guilabel:`Australia - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:27 +msgid "`l10n_au_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:28 +msgid "Payroll localisation for Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:29 +msgid ":guilabel:`Australia - Payroll with Accounting`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:30 -msgid "You can find the API Key in the :guilabel:`My Account` section of the Employment Hero platform." +msgid "`l10n_au_hr_payroll_account`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "\"Account Details\" section on the Employment Hero dashboard" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:31 +msgid "Installs the link between Australian payroll and accounting. The module also installs the modules: :guilabel:`Australian - Accounting`; :guilabel:`Australian Reports - Accounting`; and :guilabel:`Australia - Payroll`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:34 +msgid ":guilabel:`Accounting Customer Statements`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:35 -msgid "The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`. *Please do not change it.*" +msgid "`l10n_account_customer_statements`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:37 -msgid "You can find the **Business ID** in the Employment Hero URL. (i.e., `189241`)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:36 +msgid "Allows the management and sending of monthly customer statements from the partner ledger and the contact form. Also used in New Zealand." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "The Employment Hero \"Business ID\" number is in the URL" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:38 +msgid ":guilabel:`Employment Hero Australian Payroll`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:42 -msgid "You can choose any Odoo journal to post the payslip entries." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:39 +msgid "`l10n_au_keypay`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 -msgid "How does the API work?" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:40 +msgid "Synchronises all pay runs from Employment Hero with Odoo’s journal entries." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:47 -msgid "The API syncs the journal entries from Employment Hero to Odoo and leaves them in draft mode. The reference includes the Employment Hero payslip entry ID in brackets for the user to easily retrieve the same record in Employment Hero and Odoo." +msgid "The Australian chart of accounts is included in the **Australia - Accounting** module. Go to :menuselection:`Accounting --> Configuration --> Chart of Accounts` to access it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 -msgid "Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:373 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:79 +msgid ":doc:`../accounting/get_started/chart_of_accounts`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:54 -msgid "By default, the synchronization happens once per week. You can fetch the records manually by going to :menuselection:`Accounting --> Configuration --> Settings` and, in the :guilabel:`Enable Employment Hero Integration` option, click on :guilabel:`Fetch Payruns Manually`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:56 +msgid "Taxes and GST" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:58 -msgid "Employment Hero payslip entries also work based on double-entry bookkeeping." +msgid "The default Australian taxes impact the :ref:`BAS Report `, which can be accessed through :menuselection:`Accounting --> Reporting --> BAS Report`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:60 -msgid "The accounts used by Employment Hero are defined in the section :guilabel:`Payroll settings`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:61 +msgid "In Australia, the standard **Goods and Services Tax** (GST) rate is 10%, but different rates and exemptions exist for specific categories of goods and services." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 -msgid "Chart of Accounts menu in Employment Hero" +msgid "Default GST of Australia" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:65 -msgid "For the API to work, you need to create the same accounts as the default accounts of your Employment Hero business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:68 +msgid "Tax Mapping" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:3 -msgid "Austria" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:70 +msgid "Within the Australian localisation package, tax names encompass the tax rate as an integral part of their naming convention." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:8 -msgid ":ref:`Install ` the following modules to get all the features of the Austrian localization." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:73 +msgid "Despite the high amount of taxes in Odoo, these taxes are pretty similar (mostly 0% and 10%), with different tax grid variations for:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:17 -msgid ":guilabel:`Austria - Accounting`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:76 +msgid "Goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:18 -msgid "`l10n_at`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:77 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:165 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:169 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:173 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:177 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:185 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:189 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:193 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:197 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:201 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:205 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:213 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:217 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:221 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:225 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:229 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:233 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:237 +msgid "Services" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:19 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:19 -msgid "Default :ref:`fiscal localization package `." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:78 +msgid "TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:20 -msgid ":guilabel:`Austria - Accounting Reports`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:79 +msgid "TPAR without ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:21 -msgid "`l10n_at_reports`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:82 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:79 +msgid ":doc:`Taxes <../accounting/taxes>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:22 -msgid "Adds localized versions of financial reports" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:84 +msgid "Taxes including a **TPAR** mention impact not only the **BAS** report but also the **TPAR** report. Businesses from certain industries need to report payments made to subcontractors from relevant services during the financial year. Odoo combines the use of taxes and fiscal positions to report these payments on the **TPAR** report. Taxes with the mention **TPAR without ABN** are used to record amounts withheld from subcontractors without an **ABN** for the **ATO**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:23 -msgid ":guilabel:`Austrian SAF-T Export`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:91 +msgid ":ref:`TPAR `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:24 -msgid "`l10n_at_saft`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:93 +msgid "Here are the taxes for Australia in Odoo 17." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:25 -msgid "Adds the SAF-T export." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:99 +msgid "GST Name" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:30 -msgid "The following localized reports are available:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:101 +msgid "GST Scope" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:32 -msgid "Balance sheet according to `§ 224 UGB `_" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:102 +msgid "GST Type" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:33 -msgid "Profit and loss according to `§ 231 UGB `_ (Gesamtkostenverfahren)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:103 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:139 +msgid "10%" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:36 -msgid ":doc:`Accounting reporting documentation <../accounting/reporting>`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:104 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:164 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:168 +msgid "GST Purchases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:39 -msgid "SAF-T (Standard Audit File for Tax)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:106 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:110 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:114 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:118 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:122 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:126 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:130 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:134 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:138 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:166 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:170 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:174 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:182 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:186 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:190 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:194 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:198 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:202 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:206 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:210 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:214 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:218 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:222 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:226 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:230 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:234 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:238 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Purchases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:41 -msgid "The Austrian tax office may request a SAF-T. The Austrian SAF-T Export module allows exporting the report in XML format." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:107 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:143 +msgid "10% INC" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:47 -msgid "This section explains how to configure the database to ensure all the information required by the SAF-T is available. If anything is missing, a warning message listing which information is needed will be displayed during the export." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:108 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:172 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:176 +msgid "GST Inclusive Purchases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:52 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:72 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 -msgid "Company information" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:111 +msgid "10% C" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:54 -msgid "Open the database :guilabel:`Settings`. Under the :guilabel:`Companies` section, click :guilabel:`Update Info` and ensure the following fields are correctly filled in:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:112 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:180 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:184 +msgid "Capital Purchases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:57 -msgid ":guilabel:`Address`, by providing at least the following information:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:115 +msgid "0% C" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:59 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 -msgid ":guilabel:`Street`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:116 +msgid "Zero Rated Purch" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:60 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:81 -msgid ":guilabel:`City`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:119 +msgid "100% T EX" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:61 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:83 -msgid ":guilabel:`ZIP`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:120 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:196 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:200 +msgid "Purchase (Taxable Imports) - Tax Paid Separately" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:62 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 -msgid ":guilabel:`Country`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:123 +msgid "10% I" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:64 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:82 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 -msgid ":guilabel:`Phone`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:124 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:204 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:208 +msgid "Purchases for Input Taxed Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:65 -msgid ":guilabel:`Company ID` by providing your company's tax ID" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:127 +msgid "10% P" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:66 -msgid ":guilabel:`Tax ID` by providing, if you have one, your :abbr:`UID-Nummer (Umsatzsteueridentifikationsnummer)` (including the country prefix)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:128 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:212 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:216 +msgid "Purchases for Private use or not deductible" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:70 -msgid "Contact person" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:131 +msgid "100% EX" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:72 -msgid "At least one **contact person** must be linked to your company in the :guilabel:`Contacts` app, and:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:132 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:220 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:224 +msgid "GST Only on Imports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:74 -msgid "Ensure the contact type is set to :guilabel:`Individual`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:135 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:159 +msgid "10% Adj" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:75 -msgid "Select your company in the :guilabel:`Company name` field." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:136 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:228 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:232 +msgid "Tax Adjustments (Purchases)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:76 -msgid "Provide at least one phone number using the :guilabel:`Phone` or :guilabel:`Mobile` field." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:140 +msgid "GST Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:79 -msgid "Customer and supplier information" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:144 +msgid "GST Inclusive Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:81 -msgid "Using the :guilabel:`Contacts` app, fill in the :guilabel:`Address` of any partner that appears in your invoices, vendor bills, or payments." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:147 +msgid "0% EX" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:84 -msgid "For partners that are companies, fill in the VAT number (including the country prefix) in the :guilabel:`Tax ID` field." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:148 +msgid "Zero Rated (Export) Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:88 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:92 -msgid "Accounting settings" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:151 +msgid "0% EXEMPT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:90 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Austrian localization` section, fill in the following fields:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:152 +msgid "Exempt Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:93 -msgid ":guilabel:`ÖNACE-Code`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:155 +msgid "0% I" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:94 -msgid ":guilabel:`Profit Assessment Method`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:156 +msgid "Input Taxed Sales" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:97 -msgid "`ÖNACE information on the Austrian Economic Chambers website `_" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:160 +msgid "Tax Adjustments (Sales)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:101 -msgid "Chart of accounts mapping" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:163 +msgid "10% TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:103 -msgid "The Austrian SAF-T specifications define a chart of accounts (COA). All relevant accounts for the SAF-T export must be annotated with a fitting account from this COA." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:167 +msgid "10% TPAR NO ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:106 -msgid "The needed mapping information is supplied by adding tags to the accounts. For example, adding the `1000` tag to an account maps it (virtually) to the SAF-T COA account with the code `1000`. Any number can be used as long as there is an account in the SAF-T COA with that code." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:171 +msgid "10% INC TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:110 -msgid "The :guilabel:`Austria - Accounting` module adds a tag for each SAF-T COA account. Furthermore, it automatically maps many accounts from the default Austrian COA." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:175 +msgid "10% INC TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:113 -msgid "You can try exporting the SAF-T report to check if there are unmapped accounts (or mapped to multiple SAF-T accounts). A warning will be displayed if there is any issue with your configuration or the mapping. Clicking :guilabel:`View Problematic Accounts` lets you view them." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:179 +msgid "10% C TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:118 -msgid ":doc:`Chart of accounts documentation <../accounting/get_started/chart_of_accounts>`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:183 +msgid "10% C TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:121 -msgid "Exporting the SAF-T report" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:187 +msgid "0% C TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:123 -msgid "To export the SAF-T report, go to :menuselection:`Accounting --> Reports --> General Ledger`. Click the right side of the :guilabel:`PDF` button and select :guilabel:`SAF-T`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:188 +msgid "Zero Rated Purch TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/austria.rst:-1 -msgid "The SAF-T button to export the file in XML format" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:191 +msgid "0% C TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 -msgid "Belgium" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:192 +msgid "Zero Rated Purch TPAR without ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 -msgid "Install the :guilabel:`🇧🇪 Belgium` :ref:`fiscal localization package ` to get all the default accounting features of the Belgian localization, following the :abbr:`IFRS(International Financial Reporting Standards)` rules." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:195 +msgid "100% T EX TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 -msgid "You can reach the :guilabel:`Chart of accounts` by going to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:199 +msgid "100% T EX TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:22 -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." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:203 +msgid "10% I TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:377 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:79 -msgid ":doc:`../accounting/get_started/chart_of_accounts`" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:207 +msgid "100% I TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:34 -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`." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:211 +msgid "10% P TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 -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." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:215 +msgid "10% P TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 -msgid "Non-deductible taxes" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:219 +msgid "100% EX TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 -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." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:223 +msgid "100% EX TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 -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." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:227 +msgid "10% Adj TPAR" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:57 -msgid "To configure a new non-deductible tax, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes`, and click :guilabel:`New`:" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:231 +msgid "10% Adj TPAR N ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:60 -msgid ":guilabel:`Add a line` and select :guilabel:`Base` in the :guilabel:`Based On` column;" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:235 +msgid "47% WH" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:61 -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;" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:236 +msgid "Tax Withheld for Partners without ABN" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:63 -msgid "On the :guilabel:`of tax` line, select the :guilabel:`Tax Grid(s)` related to your tax;" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:243 +msgid "BAS report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 -msgid ":guilabel:`Add a line` with the **deductible** percentage in the :guilabel:`%` column;" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:245 +msgid "The **Business Activity Statement (BAS)** report is a critical tax reporting requirement for businesses registered for **Goods and Services Tax (GST)** in Australia. The **BAS** is used to report and remit various taxes to the **Australian Taxation Office (ATO)**. With the Odoo **BAS** feature, businesses can report on the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:65 -msgid "Set :guilabel:`of tax` in :guilabel:`Based On`;" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:250 +msgid "Goods and Services Tax (GST)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 -msgid "Select :guilabel:`411000 VAT recoverable` as account, and select the related tax grid." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:251 +msgid "PAYG tax withheld" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 -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." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "BAS report in Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 -msgid "With the Belgian localization, the **21% car** tax is created by default (50% non-deductible)." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:256 +msgid "The taxes for GST are collected from the **tax grid**, which is pre-configured in the system. The **tax grid** can also be manually set up for any additional special GST. Once the tax for each account is set up, the system automatically slots journal items into the correct tax category. This ensures the **BAS** report is accurate and reflective of the business's financial activities." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 -msgid "Example of not-fully deductible tax" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "GST grids in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:264 +msgid "In addition, the **BAS** report includes the **PAYG** tax withheld components (**W1** to **W5**, then **summary, section 4**). This integration ensures that all payroll-related withholding taxes are accurately captured and reflected within the report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "PAYG Tax Withheld and Summary of BAS report in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:271 +msgid "The module incorporates built-in rules that facilitate the automatic calculation of taxes for types **W1** to **W5**. For a detailed walkthrough and more information on the calculation process for these taxes, please refer to the Payroll app documentation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:276 +msgid ":ref:`Payroll `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:279 +msgid "Closing the BAS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:281 +msgid "When it is time to file the tax return with the **ATO**, click :guilabel:`Closing entry`. The tax return period can be configured in :menuselection:`configuration --> Settings --> Tax Return Periodicity`. Also, the start date of the tax return period can be defined through the **period button** (marked by a calendar icon 📅)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:287 +msgid ":doc:`Year-end closing <../accounting/reporting/year_end>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:290 +msgid "Odoo uses the *calendar quarter* rather than the Australian FY quarter, which means **July to September is Q3 in Odoo**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:293 +msgid "Before closing the entry for the first time, the default **GST payable account** and **GST receivable account** need to be set. A notification pops up and redirects the user to tax group configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:297 +msgid "Once the **GST payable** and **GST receivable** accounts are set up, the **BAS** report generates an accurate journal closing entry automatically, which balances out the GST balance with the GST clearing account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "GST accounts for the BAS report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:304 +msgid "The balance between **GST receivable** and **payable** is set against the tax clearing account defined on the tax group. The amount to be paid to or received from the **ATO** can be reconciled against a bank statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "BAS tax payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:312 +msgid "The **BAS** report is not directly submitted to the **ATO**. Odoo helps you automatically compute the necessary values in each section, with the possibility to audit them to better understand the history behind these numbers. Businesses can copy these values and enter them on the `ATO’s portal `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:320 +msgid "TPAR report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:322 +msgid "Odoo allows businesses to report payments made to contractors or subcontractors during the financial year. This is done by generating a :abbr:`TPAR (Taxable Payments Annual Report)`. If you are unsure your business needs this report, refer to the documentation provided by the `ATO `_. You can find this report in :menuselection:`Accounting --> Reporting --> Taxable Payments Annual Reports (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:331 +msgid "Under :menuselection:`Accounting --> Customers` or :menuselection:`Accounting --> Vendors`, select a your contractor and set a :guilabel:`Fiscal Position` under the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "TPAR fiscal position" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:337 +msgid "Upon billing a contact with a fiscal position set to :guilabel:`TPAR` or :guilabel:`TPAR without ABN`, the report is automatically generated in :menuselection:`Accounting --> Reporting --> Taxable Payments Annual Reports (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:341 +msgid "The report includes the **ABN**, **Total GST**, **Gross Paid**, and **Tax Withheld** from their **TPAR** subcontractors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:344 +msgid "**Total GST**: the total tax paid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:345 +msgid "**Gross Paid amounts**: shows after registering a payment for those bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:346 +msgid "**Tax Withheld**: shown if the subcontractor is registered with a fiscal position set to :guilabel:`TPAR without ABN`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:349 +msgid "The **TPAR** report can be exported to PDF, XLSX, and TPAR formats." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:354 +msgid "Customer statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:356 +msgid "Customer statements allow customers to see their financial transactions with the company over a certain period, and overdue statement details. These statements can be sent out to customers by email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Customer statement in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:363 +msgid "There are **two** ways for customers to download these statements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:365 +msgid "**From the contact form:** Customer statements are under :menuselection:`Customers --> Customers`. Select a customer, click the **gear icon (⚙)**, and then :guilabel:`Print Customer Statements`. This prints out the statement from the beginning of the month to today's date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:370 +msgid "**From the partner ledger:** This option allows for more flexibility in selecting a statement's start and end date. You can access it by going to :menuselection:`Accounting --> Reporting --> Partner Ledger`. From here, specify a date range in the **calendar menu (📅)** for the statement, hover over a partner, and click the :guilabel:`Customer Statements` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Customer statement from partner ledger report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:381 +msgid "Remittance advice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:383 +msgid "A remittance advice is a document used as proof of payment to a business. In Odoo, it can be accessed by going to :menuselection:`Accounting ‣ Vendors ‣ Payments`, selecting the payment(s), and clicking :menuselection:`Print --> Payment Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Remittance advice in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:393 +msgid "E-Invoicing via Peppol" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:395 +msgid "Odoo is compliant with Australia's and New Zealand's `PEPPOL requirements `_. You can find and set up **electronic invoicing** settings per partner under :menuselection:`Accounting --> Customers` or :menuselection:`Accounting --> Vendors`, select a partner, and click the :guilabel:`Accounting` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Peppol settings from a partner in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:404 +msgid "Validating an invoice or credit note for a partner on the PEPPOL network will download a compliant XML file that can be manually uploaded to your PEPPOL network." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:410 +msgid "ABA files for batch payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:415 +msgid "An ABA file is a digital format developed by the `Australian Bankers' Association `_. It is designed for business customers to facilitate bulk payment processing by uploading a single file from their business management software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:419 +msgid "The main advantage of using ABA files is to improve payment and matching efficiency. This is achieved by consolidating numerous payments into one file for batch processing, which can be submitted to all Australian banks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:427 +msgid "Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:429 +msgid "To enable **batch payments**, go to :menuselection:`Accounting --> Configuration --> Setting --> Batch Payment` and enable :guilabel:`Allow Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:433 +msgid "Bank journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:435 +msgid "Then, go to :menuselection:`Accounting --> Configuration --> Journals` and select the :guilabel:`Bank` journal type. In the :guilabel:`Journal Entries` tab, enter the :guilabel:`Account Number` and click :guilabel:`Create and edit`. In the pop-up window, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:440 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:477 +msgid ":guilabel:`Bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:441 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:478 +msgid ":guilabel:`Account Holder Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:442 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:479 +msgid ":guilabel:`BSB`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:443 +msgid ":guilabel:`Account Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Account Number settings for ABA in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:449 +msgid "The :guilabel:`Send Money` field must be **enabled**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:452 +msgid "The :guilabel:`Currency` field is optional." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:454 +msgid "Go back to the :guilabel:`Journal Entries` tab and fill in the following fields related to the ABA:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:456 +msgid ":guilabel:`BSB`: This field is auto-formatted from the bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:457 +msgid ":guilabel:`Financial Institution Code`: The official 3-letter abbreviation of the financial institution (e.g., WBC for Westpac)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:459 +msgid ":guilabel:`Supplying User Name`: 6-digit number provided by your bank. Contact or check your bank website if you need to know." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:463 +msgid ":guilabel:`Include Self-Balancing Transactions`: Selecting this option adds an additional" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:462 +msgid "\"self-balancing\" transaction to the end of the ABA file, which some financial institutions require when generating ABA files. Check with your bank to see if you need this option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:465 +msgid "Then, go to the :guilabel:`Outgoing Payments` tab on the same :guilabel:`Bank` type journal. Click :guilabel:`Add a line` and select :guilabel:`ABA Credit Transfer` as the **payment method**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:469 +msgid "Partners’ bank accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:471 +msgid "Go to :menuselection:`Accounting --> Customers --> Customers` or :menuselection:`Accounting --> Vendors --> Vendors` and select a partner for whom you want to add banking information. Once selected, click the :guilabel:`Accounting` tab, and under the :guilabel:`Bank Accounts` section, click :guilabel:`Add a line` to fill in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:476 +msgid ":guilabel:`Account Number` of that partner" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:480 +msgid ":guilabel:`Accounter Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:481 +msgid ":guilabel:`Send Money` defines the bank account as *trusted*, which is essential for ABA files and must be enabled if to be used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:485 +msgid "Generate an ABA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:487 +msgid "To generate an **ABA** file, :guilabel:`Create` a vendor bill (manually or from a purchase order). :guilabel:`Confirm` the bill and ensure the vendor’s banking information is set up correctly before registering a payment.." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:491 +msgid "Next, click :guilabel:`Register Payment` in the pop-up window: select the :guilabel:`Bank` journal, select :guilabel:`ABA Credit Transfer` as :guilabel:`Payment Method`, and select the right :guilabel:`Recipient Bank Account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:495 +msgid "Once payments are confirmed, they appear in :menuselection:`Accounting --> Vendors --> Payments`. Tick the box of the payments to be included in the batch, then click :guilabel:`Create Batch`. Verify all information is correct and finally :guilabel:`Validate`. Once validated, the ABA file becomes available in the **chatter** on the right." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:500 +msgid "After uploading it to your bank’s portal, an ABA transaction line will appear in your bank feed at the following bank feed iteration. You will need to reconcile it against the **batch payment** made in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:505 +msgid ":doc:`Batch Payment <../accounting/payments/batch>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:510 +msgid "Buy Now, Pay Later solutions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:512 +msgid "Buy Now, Pay Later solutions are popular payment methods for eShops in Australia. Some of these solutions are available via the `Stripe `_ and `AsiaPay `_ payment providers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:517 +msgid ":doc:`AsiaPay Payment Provider <../payment_providers/asiapay>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:518 +msgid ":doc:`Stripe Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:521 +msgid "POS terminals for Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:523 +msgid "If you wish to have a direct connection between Odoo and your PoS terminal in Australia, you *must* have a **Stripe** terminal. Odoo supports the **EFTPOS** payment solution in Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:527 +msgid "You do not need a Stripe payment terminal to use Odoo as your main PoS system. The only drawback of not using Stripe is that cashiers must manually enter the final payment amount on the terminal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:532 +msgid ":doc:`Stripe Odoo Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:533 +msgid ":doc:`Stripe Odoo Payment Terminal `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:534 +msgid "`Stripe Dashboard `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:535 +msgid "`Stripe Terminal `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:540 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:543 +msgid "Odoo is currently not compliant with STP Phase 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:546 +msgid "Create your employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:548 +msgid "To create an **employee form** and fill in mandatory information, go to the **Employees** app and click :guilabel:`Create`. In the :guilabel:`HR Settings` tab, you can input the mandatory information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:552 +msgid ":guilabel:`TFN Status`: if the employee provides a TFN, make sure to add it to the “TFN” field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:553 +msgid ":guilabel:`Non-resident`: if the employee is a foreign resident" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:554 +msgid ":guilabel:`Tax-free Threshold`: if the employee is below or above the threshold" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:555 +msgid ":guilabel:`HELP / STSL`: for all types of study and training support loans (e.g. HELP, VSL, SSL…)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:556 +msgid ":guilabel:`Medicare levy Deduction`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:557 +msgid ":guilabel:`Medicare levy Exemption`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:558 +msgid ":guilabel:`Withholding for Extra Pay`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:559 +msgid "..." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:562 +msgid "Manage Australian contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:564 +msgid "Once the employee form has been created, ensure the contract is enabled by clicking the :guilabel:`Contracts` smart button or by going to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:569 +msgid "Only one contract can be active simultaneously per employee, but an employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:572 +msgid "Contractual information related to Australia can be found in the following **three** places:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:574 +msgid "Before assigning a salary amount, pay frequency, and other important details to a contract, defining the **salary structure**, **start date**, and **work entry** source is important. In Australia, a \"Salary Structure\" is employed to specify the tax schedule applicable to that contract, as defined by the Australian Taxation Office (ATO). Most contracts will fall under the following **three structures**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:580 +msgid "**Regular (Schedule 1)**: the great majority of Australian employees will fall in this category; hence, this structure is assigned by default to all contracts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:582 +msgid "**Working holiday makers (Schedule 15)**. When employing working holiday makers (WHMs), other taxes apply. For detailed information on these specific tax implications, refer to the documentation provided by the **ATO**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:585 +msgid "**No TFN**. Choose this structure if the employee hasn’t provided a **TFN** for over **28** days." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Employees form in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:592 +msgid "The structures **Horticulture/Shearing (Schedule 2)** and **Artists and Performers (Schedule 3)** are only partially complete, and proper tests should be performed before using them to pay employees in your production database. Send your feedback to au-feedback@mail.odoo.com." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:596 +msgid "The field :guilabel:`Work Entry Source` is also significant and defines how **working hours** and **days** are accounted for in the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:599 +msgid ":guilabel:`Working Schedule`: work entries are automatically generated based on the employee’s working schedule, starting from the contract's start date.. For example, let’s assume that an employee works 38 hours a week, and their contract’s begins on January 1st. Today is January 16th, and the user generates a pay run from January 14th to 20th. The working hours on the payslip will be automatically calculated to be 38 hours (5 * 7.36 hours) if no leave is taken." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:604 +msgid ":guilabel:`Attendances`: The default working schedule is ignored, and work entries are only generated after clocking in and out of the attendance app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:606 +msgid ":guilabel:`Planning`: The default working schedule is ignored, and work entries are generated from planning shifts only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:610 +msgid "Additional configurations are necessary to ensure that Odoo’s payslips automatically compute various **penalty rates** as defined by an **award (overtime rate, public holiday rate, etc)**. To create these configurations, create new work-entry types for each penalty rate and then assign a penalty rate in % to each. Once this one-time configuration is done, work entries can be manually imported for each period, and Odoo will separate the pay items and rates on the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:618 +msgid "Timesheets do not impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:620 +msgid "The :guilabel:`Salary Information` tab contains a few essential fields impacting the frequency of pay runs and the management of payslip rules in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:623 +msgid ":guilabel:`Wage Type`: Select the :guilabel:`Fixed Wage` pay type for full-time and part-time employees. For casual workers and other :guilabel:`Hourly Wage` type. For employees being paid hourly, make sure to define the correct **casual loading**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:626 +msgid ":guilabel:`Schedule Pay`: In Australia, only the following pay run frequencies are accepted: **daily, weekly, bi-weekly (or fortnightly), monthly, and quarterly**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:628 +msgid ":guilabel:`Wage` (/period): Assign a wage to the contract according to their pay frequency. On payslips, the corresponding annual and hourly rates will be automatically computed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:632 +msgid "For hourly workers, please note that the hourly wage should exclude casual loading." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:634 +msgid "The :guilabel:`Australia` tab. Most of the fields in this tab are used for **Single Touch Payroll** (or **STP**) reporting, which requires a thorough understanding of several details from an employee’s contract. Review the information on this tab before moving forward with pay runs. This includes the following **four** fields which impact payslip computations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:639 +msgid ":guilabel:`Withholding Variation`: use this field in case the employee’s withholding must be varied upward or downward according to their circumstances. E.g., if employee X benefits from a 25% withholding variation, their percentage of tax withheld will vary from whatever amount they were supposed to pay according to their salary structure and situation to a fixed 25%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:643 +msgid ":guilabel:`Leave Loading`: if the employee benefits from a regular leave loading, the value set in the field :guilabel:`Leave Loading Rate` (e.g., 17.5%) is added to any amount earned when taking annual or long service leaves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:646 +msgid ":guilabel:`Salary Sacrifice Superannuation`: any amount added to this field is deducted, per pay frequency, from the employee’s basic salary before the computation of the gross salary. Then, this amount is added to the super guarantee line of their payslip. E.g., if employee Y earns 5,000 AUD per month and sacrifices 300 AUD to superannuation, their gross salary will be 4,700 AUD, and 300 AUD will be added on top of their normal super contributions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:651 +msgid ":guilabel:`Salary Sacrifice Other`: any amount added to this field is deducted, per pay frequency, from the employee’s basic salary before the computation of the gross salary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:654 +msgid "Once all important information has been entered, ensure the transition of the contract's status from \"New\" to \"Running\" to facilitate its use in pay runs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "\"Australia\" payroll tab in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:661 +msgid "Assign superannuation accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:663 +msgid "Upon receipt of superannuation details from a new employee, ensure the creation of a new account in :menuselection:`Payroll --> Configuration --> Super Accounts` to link it to the employee. Input the :guilabel:`Super Fund`, :guilabel:`Member Since` date, and :guilabel:`TFN` number of the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:667 +msgid "Suppose the employee uses a superannuation fund that does not exist in the database yet. In that case Odoo creates a new one and centralises basic information about this fund, such as its **ABN**, **address**, type (**APRA** or **SMSF**), **USI**, and **ESA**. Super funds can be created or imported in :menuselection:`Payroll --> Configuration --> Super Funds`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:673 +msgid "Odoo is currently not **SuperStream-compliant**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:676 +msgid "Create pay runs with payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:678 +msgid "Odoo can create pay runs in **two** ways: via **batch** or via **individual** payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:681 +msgid "Create a batch of payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:683 +msgid "When preparing to generate employees’ draft payslips (e.g., at the end of every week, fortnight, or month), navigate to :menuselection:`Payroll --> Payslips --> Batches` and click :guilabel:`New`. Fill in the necessary info, click :guilabel:`Generate Payslips`, select the :guilabel:`Salary Structure`, :guilabel:`Department`, :guilabel:`Employees`, and :guilabel:`Generate`. This method allows the creation of multiple payslips corresponding to each employee in a single batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:690 +msgid "Give the batch a name. (E.g., `2024 – Weekly W1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:691 +msgid "Choose the pay run's start and end date. (E.g., 01/01/2024 to 07/01/2024)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:692 +msgid "Click on :guilabel:`Generate`. A pop-up window asks to confirm which employees should be included in the batch. By default, all active employees are included. You can leave :guilabel:`Salary Structure` field blank as Odoo automatically selects the structure linked to each employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:696 +msgid "The batch creates as many payslips as there are employees. There is no limit to the number of payslips created in a batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:698 +msgid "Verify important information on each payslip. After payslips from a batch have been generated, there is no need to manually compute payslip lines; Odoo does it for you." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:702 +msgid "Create an individual payslip" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:704 +msgid "In cases where the pay run does not fall into the category of regular payslips, the option exists to create a pay run dedicated to a single employee. Go to :menuselection:`Payroll --> Payslips --> All Payslips` and click :guilabel:`New`. Employ this method when processing **one-time payments** for employees, including **return-to-work** payments (**ATO Schedule 4**), **employment termination** payments (**ATO Schedule 7 and 11**), and **commissions and bonuses** (**ATO Schedule 5**). When generating an individual payslip, make sure to proceed with the following steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:711 +msgid "Select an :guilabel:`Employee`; their :guilabel:`Contract` will be filled out automatically" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:712 +msgid "Add a pay :guilabel:`Period`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:713 +msgid "Select a salary :guilabel:`Structure` (e.g., return-to-work payment)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:714 +msgid "Unlike payslips generated from a batch, the payroll user must click the :guilabel:`Compute Sheet` button to generate payslip lines" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "One-time payments in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:721 +msgid "Understand payslip features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:723 +msgid "The same features apply no matter how payslips are created (individually or via batch)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:725 +msgid "Depending on how work entries are created, the :guilabel:`Worked Days & Inputs` table automatically shows the number of days and hours the employee worked during the payslip period next to the corresponding total gross amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:730 +msgid "There is one line per work entry type, meaning **paid** and **unpaid time-off**, in addition to custom **hourly penalty rates** (overtime, public holidays, etc.) which are automatically added to the table." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Worked days and hours in Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:737 +msgid "In the :guilabel:`Other Inputs` section, You can add entries such as **allowances** and **extra pay** items in the :guilabel:`Other Inputs` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:740 +msgid "To incorporate various **allowances** into an employee's payslip, create **allowances** in :menuselection:`Payroll --> Configuration --> Other Input Types`. Once created, tick the :guilabel:`Is an Allowance` checkbox for the involved allowances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:745 +msgid "Withholding for allowances is not computed automatically. The payroll user has to use the field :guilabel:`Withholding for allowance` under the other inputs table to manually add the total amount to be withheld across all allowances on that payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:749 +msgid "**Extra pay** items are other inputs added to the **payslip’s gross** and, as a result, to the **withholding amount**. An example lies in regular sales commissions, taxed at the same rate as the regular salary (unlike discretionary bonuses, which fall under the ATO’s Schedule 5 and its corresponding salary structure). To configure such a custom pay item, go to :menuselection:`Payroll --> Configuration --> Other Input Types` and create a new entry with the code **EXTRA**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Extra pay item input type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:759 +msgid "In the :guilabel:`Salary Computation` tab, the payroll user can verify whether all the pay rules have been computed correctly as per employee, contract and salary structure. Here are a few guidelines to better understand the data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Salary computation in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:766 +msgid "**Basic salary:** amount from which tax-deductible lines can be subtracted" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:767 +msgid "**Gross salary:** amount subject to the taxes defined by the salary structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:768 +msgid "**Withholding:** tax amount to be paid to the **ATO**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:769 +msgid "**Net salary:** amount to be paid to the employee’s bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:770 +msgid "**Superannuation Guarantee:** amount to be provisioned for quarterly payments to the employee’s super account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:772 +msgid "**Allowances & Extra pay items:** these lines will show if other inputs are added to the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:773 +msgid "**Other lines:** depending on the employee and contract specifics (Medicare, child support, salary, sacrifice, etc.)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:776 +msgid "When satisfied with the payslip, click :guilabel:`Create Draft entry` to generate a draft accounting journal entry that the accountant can review. Note that in the case of a payslip batch, this accounting entry will sum up balances from all payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:781 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:783 +msgid "After a batch or a payslip’s journal entry has been posted, the company can pay their employees. The user can choose between **two** different **payment methods**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:786 +msgid "Pay the employee in batch via **ABA** files. This is **only** possible from the **payslip batch** level. Ensure the batch’s journal entry has been posted to generate the **ABA** file. From the batch form view, click :guilabel:`Create ABA File` and choose the desired bank journal. The newly generated **ABA** file becomes available for download in the field :guilabel:`ABA File`. It is possible to re-generate the ABA file after applying corrections to existing payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:793 +msgid "It is always possible to include an individual payslip into an existing batch in an **ABA** file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:797 +msgid "An ABA file can only be generated if both the company’s bank account and each employee’s bank account have been properly :ref:`configured `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:800 +msgid "From the employee's payslip (:menuselection:`Payroll --> Payslips`), once the payslip's journal entry has been posted, click :guilabel:`Register Payment`. The process is the same as :doc:`paying vendor bills <../accounting/payments>`: select the desired bank journal and payment method, then later reconcile the payment with the corresponding bank statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:806 +msgid "One-time payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:808 +msgid "Certain payments, such as **Return-to-Work** payments and **Employment Termination Payments** **(ETP)**, are processed only once and require a slightly different approach." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:812 +msgid "Return-to-Work payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:814 +msgid "A **Return-to-Work** payment is a payment made to an employee to resume working. To process one, create an individual payslip, select the employee, and modify its **regular structure** to :guilabel:`Australia: Return to work`. Then, add the **gross amount** of that payment in the :guilabel:`Other Inputs` section and compute the payslip. Odoo automatically computes the **PAYG withholding**, the **net amount**, and the **super guarantee** corresponding to that payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Return-to-work payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:824 +msgid "Termination payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:826 +msgid "Before proceeding with the employee’s ETP, make sure that a **Contract End Date** has been set on that employee’s contract so that Odoo can automatically compute the final prorated salary of that employee for the current month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:830 +msgid "First, create the final salary for that employee this month. To do so, create an individual payslip. If the contract end date is set correctly, Odoo will automatically compute the prorated salary up to the final payslip date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Termination payment worked days computation in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:838 +msgid "We recommend creating a batch on the fly for that payslip, in which the ETP is added as a second payslip of that same batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:841 +msgid "Create a second individual payslip and include it in the same batch. Change the salary structure on that payslip to :guilabel:`Australia: Termination Payments`. Before computing the sheet, it is important to provide the payslip with termination details ." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Termination payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:848 +msgid ":guilabel:`Genuine` or :guilabel:`Non-Genuine Redundancy`. This choice impacts the amounts and caps defined per **ETP** type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:850 +msgid "**ETP types**: see the full list of termination payment types in :guilabel:`Other Input Types` by filtering by `ETP Type is Set`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Payslip other inputs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:856 +msgid "Add the relevant **ETP type** in the :guilabel:`Other Inputs` table of the payslip, then compute the payslip. Odoo computes the **gross ETP**, the **withholding**, the **unused leaves**, and the **net salary** according to the rules defined on the **ETP**, the **employee**, and their **contract**. Once payment for both payslips is ready to be processed, an **ABA** file can be created directly from the batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:865 +msgid "Employment Hero Australian Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:867 +msgid "If your business is already up and running with `Employment Hero `_, you can use our connector as an alternative payroll solution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:870 +msgid "The Employment Hero module synchronises payslip accounting entries (e.g., expenses, social charges, liabilities, taxes) automatically from Employment Hero to Odoo. Payroll administration is still done in Employment Hero. We only record the **journal entries** in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:875 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:880 +msgid ":ref:`Activate ` the :guilabel:`Employment Hero Australian Payroll` module (`l10n_au_keypay`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:882 +msgid "Configure the **Employment Hero API** by going to :menuselection:`Accounting --> Configuration --> Settings`. More fields become visible after clicking on :guilabel:`Enable Employment Hero Integration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:890 +msgid "You can find the API Key in the :guilabel:`My Account` section of the Employment Hero platform." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:895 +msgid "The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:898 +msgid "Do not change the **pre-filled Payroll URL**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:900 +msgid "You can find the **Business ID** in the Employment Hero URL. (i.e., `189241`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "The Employment Hero \"Business ID\" number is in the URL" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:905 +msgid "You can choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:908 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:910 +msgid "The API syncs the journal entries from Employment Hero to Odoo and leaves them in draft mode. The reference includes the Employment Hero payslip entry ID in brackets for the user to easily retrieve the same record in Employment Hero and Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:917 +msgid "By default, the synchronisation happens once per week. You can fetch the records manually by going to :menuselection:`Accounting --> Configuration --> Settings` and, in the :guilabel:`Enable Employment Hero Integration` option, click on :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:921 +msgid "Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:923 +msgid "The accounts used by Employment Hero are defined in the section :guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:928 +msgid "For the API to work, you need to create the same accounts as the default accounts of your Employment Hero business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:3 +msgid "Austria" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:8 +msgid ":ref:`Install ` the following modules to get all the features of the Austrian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:17 +msgid ":guilabel:`Austria - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:18 +msgid "`l10n_at`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:19 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:19 +msgid "Default :ref:`fiscal localization package `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:20 +msgid ":guilabel:`Austria - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:21 +msgid "`l10n_at_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:22 +msgid "Adds localized versions of financial reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:23 +msgid ":guilabel:`Austrian SAF-T Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:24 +msgid "`l10n_at_saft`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:25 +msgid "Adds the SAF-T export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:30 +msgid "The following localized reports are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:32 +msgid "Balance sheet according to `§ 224 UGB `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:33 +msgid "Profit and loss according to `§ 231 UGB `_ (Gesamtkostenverfahren)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:36 +msgid ":doc:`Accounting reporting documentation <../accounting/reporting>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:39 +msgid "SAF-T (Standard Audit File for Tax)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:41 +msgid "The Austrian tax office may request a SAF-T. The Austrian SAF-T Export module allows exporting the report in XML format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:47 +msgid "This section explains how to configure the database to ensure all the information required by the SAF-T is available. If anything is missing, a warning message listing which information is needed will be displayed during the export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:52 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:68 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 +msgid "Company information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:54 +msgid "Open the database :guilabel:`Settings`. Under the :guilabel:`Companies` section, click :guilabel:`Update Info` and ensure the following fields are correctly filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:57 +msgid ":guilabel:`Address`, by providing at least the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:59 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:76 +msgid ":guilabel:`Street`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:60 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +msgid ":guilabel:`City`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:61 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:79 +msgid ":guilabel:`ZIP`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:62 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 +msgid ":guilabel:`Country`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:64 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:82 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 +msgid ":guilabel:`Phone`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:65 +msgid ":guilabel:`Company ID` by providing your company's tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:66 +msgid ":guilabel:`Tax ID` by providing, if you have one, your :abbr:`UID-Nummer (Umsatzsteueridentifikationsnummer)` (including the country prefix)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:70 +msgid "Contact person" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:72 +msgid "At least one **contact person** must be linked to your company in the :guilabel:`Contacts` app, and:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:74 +msgid "Ensure the contact type is set to :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:75 +msgid "Select your company in the :guilabel:`Company name` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:76 +msgid "Provide at least one phone number using the :guilabel:`Phone` or :guilabel:`Mobile` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:79 +msgid "Customer and supplier information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:81 +msgid "Using the :guilabel:`Contacts` app, fill in the :guilabel:`Address` of any partner that appears in your invoices, vendor bills, or payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:84 +msgid "For partners that are companies, fill in the VAT number (including the country prefix) in the :guilabel:`Tax ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:88 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +msgid "Accounting settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:90 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Austrian localization` section, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:93 +msgid ":guilabel:`ÖNACE-Code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:94 +msgid ":guilabel:`Profit Assessment Method`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:97 +msgid "`ÖNACE information on the Austrian Economic Chambers website `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:101 +msgid "Chart of accounts mapping" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:103 +msgid "The Austrian SAF-T specifications define a chart of accounts (COA). All relevant accounts for the SAF-T export must be annotated with a fitting account from this COA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:106 +msgid "The needed mapping information is supplied by adding tags to the accounts. For example, adding the `1000` tag to an account maps it (virtually) to the SAF-T COA account with the code `1000`. Any number can be used as long as there is an account in the SAF-T COA with that code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:110 +msgid "The :guilabel:`Austria - Accounting` module adds a tag for each SAF-T COA account. Furthermore, it automatically maps many accounts from the default Austrian COA." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:79 -msgid ":doc:`Taxes <../accounting/taxes>`" +#: ../../content/applications/finance/fiscal_localizations/austria.rst:113 +msgid "You can try exporting the SAF-T report to check if there are unmapped accounts (or mapped to multiple SAF-T accounts). A warning will be displayed if there is any issue with your configuration or the mapping. Clicking :guilabel:`View Problematic Accounts` lets you view them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:118 +msgid ":doc:`Chart of accounts documentation <../accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:121 +msgid "Exporting the SAF-T report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:123 +msgid "To export the SAF-T report, go to :menuselection:`Accounting --> Reports --> General Ledger`. Click the right side of the :guilabel:`PDF` button and select :guilabel:`SAF-T`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:-1 +msgid "The SAF-T button to export the file in XML format" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 +msgid "Install the :guilabel:`🇧🇪 Belgium` :ref:`fiscal localization package ` to get all the default accounting features of the Belgian localization, following the :abbr:`IFRS(International Financial Reporting Standards)` rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 +msgid "You can reach the :guilabel:`Chart of accounts` by going to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:22 +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." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:34 +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`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +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." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +msgid "Non-deductible taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +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." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +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." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:57 +msgid "To configure a new non-deductible tax, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes`, and click :guilabel:`New`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:60 +msgid ":guilabel:`Add a line` and select :guilabel:`Base` in the :guilabel:`Based On` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:61 +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;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:63 +msgid "On the :guilabel:`of tax` line, select the :guilabel:`Tax Grid(s)` related to your tax;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +msgid ":guilabel:`Add a line` with the **deductible** percentage in the :guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:65 +msgid "Set :guilabel:`of tax` in :guilabel:`Based On`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +msgid "Select :guilabel:`411000 VAT recoverable` as account, and select the related tax grid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 +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." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 +msgid "With the Belgian localization, the **21% car** tax is created by default (50% non-deductible)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Example of not-fully deductible tax" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:80 @@ -13555,210 +14890,468 @@ msgstr "" msgid "Once your **SODA** files are imported, the entries are created automatically in your 'salary' journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 -msgid "Import SODA files" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Import SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:246 +msgid "CodaBox" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:248 +msgid "**CodaBox** is a service that allows Belgian accounting firms accessing their clients' bank information and statements. Odoo provides a way to import such statements automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:252 +msgid "As an accounting firm, you must manage your clients on separate databases and configure them individually to avoid mixing up their data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:258 +msgid "The configuration must be done on each client database. In the following instructions, we will refer to your client's company as *Company* and to your accounting firm as *Accounting Firm*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:262 +msgid "You must first :ref:`Install ` :guilabel:`CodaBox` and :guilabel:`CodaBox Bridge` to start." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:266 +msgid "Make sure the company settings are correctly configured, i.e., the country is set to :guilabel:`Belgium`, the :guilabel:`Tax ID` and :guilabel:`Accounting Firm` fields are filled, as well as the :guilabel:`Tax ID` of the accounting firm (unless it is the same as the company's :guilabel:`Tax ID`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:272 +msgid "Configure the Journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:276 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:351 +msgid "For CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:278 +msgid ":doc:`Create a new bank journal <../accounting/bank>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:279 +msgid "Set the right IBAN in the :guilabel:`Account Number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:280 +msgid "Select :guilabel:`CodaBox synchronisation` as the :guilabel:`Bank Feed`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a CODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:286 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:361 +msgid "For SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:288 +msgid "Create a new miscellaneous journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:289 +msgid "Go to :menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 +msgid "Select the journal you just created in the SODA journal field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a SODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:299 +msgid "Configure the Connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:301 +msgid "First, you must select which users can access the **CodaBox** connection settings. To do so, go to :menuselection:`Settings --> Users & Companies --> Groups`, and search for the group :guilabel:`Allow to show and modify the CodaBox Connection Settings`. Add the users you want to this group. By default, only the :guilabel:`Administrator` is part of this group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:306 +msgid "Then, to configure the connection itself, go to :menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:309 +msgid "The procedure differs depending on whether **CodaBox** is being setup for a first client or an additional one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 +msgid "First connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:316 +msgid "Click on :guilabel:`Connect`, where you are redirected to the **CodaBox** platform, here validate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:318 +msgid "Once redirected back to Odoo, the :guilabel:`Status` should be set to :guilabel:`Connected` and a new field :guilabel:`Access Token` should appear." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configured connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 +msgid "This :guilabel:`Access Token` will be used to create new connections for other clients without having to validate the connection again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:329 +msgid "Following connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:331 +msgid "Copy the :guilabel:`Access Token` from a previous connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 +msgid "Click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +msgid "The **CodaBox** connection linked to the :guilabel:`Access Token` should still exist, therefore there is no need to validate the connection again. A new and different :guilabel:`Access Token` is generated, and the :guilabel:`Status` should be set to :guilabel:`Connected`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:340 +msgid "By having a different :guilabel:`Access Token` for each client, you can easily revoke the access of a client to your CodaBox account without affecting the other clients. One client cannot interfere with another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 +msgid "Synchronisation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:347 +msgid "Once the connection is established, Odoo can be synchronized with CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:353 +msgid "CODA files are automatically imported from CodaBox every 12 hours. You do not have to do anything. However, if you wish, it can also be done manually, by clicking on :guilabel:`Fetch CODA's` in the Accounting Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch CODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:363 +msgid "SODA files are automatically imported from CodaBox once a day as draft. You do not have to do anything. However, if you wish, it can also be done manually, by clicking on :guilabel:`Fetch SODA's` in the Accounting Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 +msgid "By default, if an account in the SODA is not mapped to an account in Odoo, the Suspense Account (499000) is used and a note is left in the created journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch SODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 +msgid "You can access the mapping between the SODA accounts and the Odoo accounts by clicking on the :guilabel:`SODA Mapping` button in :menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:380 +msgid "The connection between Odoo and CodaBox can be revoked by using the :guilabel:`Revoke` button in the CodaBox settings, which will revoke the link on Odoo's side only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:384 +msgid "If you have multiple connections, you will still be able to use the Access Token of one of them to easily reconnect Odoo and CodaBox for another client." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:388 +msgid "However, if you have only one (remaining) connection, you will not be able to use its Access Token to create new connections. In that case, you will have to revoke the connection from the CodaBox platform too, and then recreate a new one following the steps in the :ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 +msgid "Potential issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "CodaBox is not configured. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "Either the Company VAT of the Accounting Firm VAT is not set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "It seems that the fiduciary VAT number you provided is not valid. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "Either the Company VAT of the Accounting Firm VAT is in the wrong format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "It seems that the fiduciary VAT number you provided does not exist in CodaBox. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "The Accounting Firm VAT number you provided is not registered in CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 +msgid "Error while connecting to the IAP server. Please contact Odoo support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:407 +msgid "It seems that Odoo's IAP server is down or unreachable. Please contact Odoo support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:414 +msgid "It seems that your CodaBox connection is not valid anymore. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 +msgid "It seems that you have either revoked the access of Odoo to your CodaBox account, or that you have not completed the configuration process. In this case, you must click on the :guilabel:`Revoke connection` button in the settings, and follow again the steps in the :ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:423 +msgid "A previous CodaBox registration already exists. Paste the access token from a previous connection here. Odoo will generate a new one, exclusive to this database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 +msgid "It seems that you have already your Accounting Firm with Odoo, but that the Access Token is either not filled or wrong. You should follow the steps in the :ref:`following connection ` tab section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 +msgid "If you have lost your Access Token, you have to go on the CodaBox platform, and revoke the access of Odoo to your CodaBox account. Then, you will have to follow the steps in the :ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "The provided access token is not valid for this fiduciary. Please check your configuration. If you have lost your access token, please contact Odoo support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "Same as above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:433 +msgid "It seems that no connection linked to your database/VAT number exists. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 +msgid "You may obtain this error when revoking or trying to fetch files from CodaBox if the pair (Accounting Firm VAT, Company VAT) is not registered yet. This may happen if you have changed the company VAT after the connection was established for instance. For security reasons, you have to recreate a connection for this company VAT by following the steps in the :ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:438 +msgid "No files were found. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 +msgid "This may occur if the company VAT has changed after the connection was established. In that case, you must click on the :guilabel:`Revoke connection` button in the settings, and recreate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:443 +msgid "It seems you have already created a connection to CodaBox with this fiduciary. To create a new connection, you must first revoke the old one on myCodaBox portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:441 +msgid "You must go on the CodaBox platform, and revoke the access of Odoo to your CodaBox account. Then, you will have to follow the steps in the :ref:`first connection ` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:246 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:446 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 msgid "Electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:248 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:448 msgid "Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing format. To enable it for a customer, go to :menuselection:`Accounting --> Customers --> Customers`, open their contact form, and under the :guilabel:`Accounting` tab, select the :guilabel:`Peppol BIS Billing 3.0` format." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:253 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:453 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 #: ../../content/applications/finance/fiscal_localizations/italy.rst:94 msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:258 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 msgid "Cash discount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:260 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:460 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:263 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 msgid "To apply the right tax amount and report it correctly in your VAT return, set the tax reduction as :guilabel:`Always (upon invoice)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:267 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:467 msgid ":doc:`../accounting/customer_invoices/cash_discounts`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:272 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 msgid "Fiscal certification: POS restaurant" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:274 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:474 msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:278 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 msgid "This government-certified system entails the use of a :ref:`certified POS system `, along with a device called a :ref:`Fiscal Data Module ` (or **black box**) and a :ref:`VAT Signing Card `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:283 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:483 msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:289 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:489 msgid "Certified POS system" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:291 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:491 msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and **Odoo.sh**. Please refer to the following table to ensure that your POS system is certified." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:299 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:499 #: ../../content/applications/finance/payment_providers/stripe.rst:17 msgid "Odoo Online" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:300 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:500 msgid "Odoo.sh" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:301 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:501 msgid "On-Premise" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:302 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:502 msgid "Odoo 16.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:303 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:304 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:311 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:312 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:315 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:316 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:503 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:504 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:511 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:512 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:515 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:516 msgid "Certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:305 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:307 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:308 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:309 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:313 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:317 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:505 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:507 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:508 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:509 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:513 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:517 msgid "Not certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:306 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:506 msgid "Odoo 15.2" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:310 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:510 msgid "Odoo 15.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:514 msgid "Odoo 14.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:320 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:520 msgid ":doc:`/administration/maintain/supported_versions`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:322 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:522 msgid "A `certified POS system `_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 msgid "On a certified POS, you cannot:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:328 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:528 msgid "Set up and use the **global discounts** feature (the `pos_discount` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:330 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:530 msgid "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 msgid "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:333 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:533 msgid "Modify prices in order lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 msgid "Modify or delete order lines in POS orders." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:335 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:535 msgid "Sell products without a valid VAT number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:336 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 msgid "Use a POS that is not connected to an IoT box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:338 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:538 msgid "The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` feature must be activated and set to a :guilabel:`Rounding Precision` of `0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:341 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:541 msgid "Taxes must be set as included in the price. To set it up, go to :menuselection:`Point of Sale --> Configuration --> Settings`, and from the :guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form by clicking the arrow next to the default sales tax field. There, click :guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:545 msgid "At the start of a POS session, users must click :guilabel:`Work in` to clock in. Doing so allows the registration of POS orders. If users are not clocked in, they cannot make POS orders. Likewise, they must click :guilabel:`Work Out` to clock out at the end of the session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:350 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:550 msgid "If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you cannot use it again without it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:356 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:556 msgid "Fiscal Data Module (FDM)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:358 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:558 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:364 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:564 msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 `_ is supported by Odoo. `Contact the manufacturer (GCV BMC) `_ to order one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:372 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:572 msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:374 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:574 msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 msgid "an RS-232 serial null modem cable per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:376 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:576 msgid "an RS-232 serial-to-USB adapter per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:377 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:577 msgid "an :ref:`IoT Box ` (one IoT box per FDM); and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:378 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:578 msgid "a receipt printer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:383 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:583 msgid "Black box module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:385 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:585 msgid "As a pre-requisite, :ref:`activate ` the `Belgian Registered Cash Register` module (technical name: `pos_blackbox_be`)." msgstr "" @@ -13766,7 +15359,7 @@ msgstr "" msgid "black box modules for belgian fiscal certification" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:391 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:591 msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and fill in the :guilabel:`INSZ or BIS number` field." msgstr "" @@ -13774,35 +15367,35 @@ msgstr "" msgid "ISNZ or BIS number field on employee form" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:601 msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:405 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:605 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:611 msgid "IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:413 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:613 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 `_ and provide the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:617 msgid "your VAT number;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:418 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:618 msgid "your company's name, address, and legal structure; and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:419 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:619 msgid "the Mac address of your IoT Box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:621 msgid "Once your IoT box is certified, :doc:`connect <../../productivity/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." msgstr "" @@ -13810,19 +15403,19 @@ msgstr "" msgid "Hardware status page on a registered IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:428 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:628 msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:433 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:633 msgid "To be able to use an FDM, you must at least connect one :guilabel:`Receipt Printer`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:438 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:638 msgid "VAT signing card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:440 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:640 msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration `_." msgstr "" @@ -14210,10 +15803,6 @@ msgstr "" msgid "Please note that each |API| call incurs a cost. Be mindful of the actions that trigger these calls to manage costs effectively." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:306 -msgid "Tax computation" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 msgid "Tax calculations on quotations and sales orders" msgstr "" @@ -14351,7 +15940,7 @@ msgid "All of the fields available on the invoice used to issue an electronic in msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:390 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:599 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" @@ -14527,7 +16116,7 @@ msgid "Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:40 -msgid ":guilabel:`Chile - E-invoiving`" +msgid ":guilabel:`Chile - E-invoicing`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:41 @@ -14551,7 +16140,7 @@ msgid "Includes all technical and functional requirements to generate and receiv msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:48 -msgid ":guilabel:`Electronic Esports of Goods for Chile`" +msgid ":guilabel:`Electronic Exports of Goods for Chile`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:49 @@ -14563,12 +16152,10 @@ msgid "Includes technical and functional requirements to generate electronic inv msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:52 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:56 msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:53 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:57 msgid "`l10n_cl_edi_stock`" msgstr "" @@ -14577,131 +16164,127 @@ msgid "Includes all technical and functional requirements to generate delivery g msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:58 -msgid "Includes all technical and functional requirements to generate delivery guides online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:62 msgid "Odoo automatically installs the appropriate package for the company according to the country selected at the creation of the database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:64 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:60 msgid "The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:67 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:63 msgid "All features are only available if the company already completed the `SII Sistema de Facturación de Mercado `_ certification process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:70 msgid "Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure the following company information is up-to-date and correctly filled in:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:73 msgid ":guilabel:`Company Name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 msgid ":guilabel:`Address`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 msgid ":guilabel:`State`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:86 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 msgid ":guilabel:`Tax ID`: enter the identification number for the selected :ref:`Taxpayer Type `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 msgid ":guilabel:`Activity Names`: select up to four activity codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:89 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:85 msgid ":guilabel:`Company Activity Description`: enter a short description of the company's activity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:90 msgid "Next, navigate to :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` and follow the instructions to configure the:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:97 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:93 msgid ":ref:`Fiscal information `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:98 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 msgid ":ref:`Electronic invoice data `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:99 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:95 msgid ":ref:`DTE incoming email server `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:100 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:96 msgid ":ref:`Signature certificates `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:101 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 msgid "Fiscal information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:103 msgid "Configure the following :guilabel:`Tax payer information`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:111 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 msgid ":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to customers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:108 msgid ":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees receipt (Boleta)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:113 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 msgid ":guilabel:`End consumer`: only issues receipts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:114 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:110 msgid ":guilabel:`Foreigner`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:116 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 msgid ":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de Impuestos Internos)` regional office" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:118 msgid "Electronic invoice data" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:124 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:120 msgid "Select your :guilabel:`SII Web Services` environment:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 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)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:130 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 msgid ":guilabel:`SII - Production`: for production databases." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:131 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:127 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:136 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:132 msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:138 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:134 msgid ":guilabel:`SII Resolution N°`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:139 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:135 msgid ":guilabel:`SII Resolution Date`" msgstr "" @@ -14709,71 +16292,71 @@ msgstr "" msgid "Required information for electronic invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:148 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:144 msgid "DTE incoming email server" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:150 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:146 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:153 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`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 msgid "Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click :guilabel:`New` to add a server and fill in the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:160 msgid ":guilabel:`Name`: give the server a name." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 msgid ":guilabel:`Server Type`: select the server type used." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:163 msgid ":guilabel:`IMAP Server`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:168 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 msgid ":guilabel:`POP Server`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:169 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:175 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 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*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:178 msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:180 msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:185 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:181 msgid ":guilabel:`Port`: enter the server port." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:186 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 msgid ":guilabel:`SSL/TLS`: enable this option if connections are encrypted using the SSL/TLS protocol." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:187 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:183 msgid ":guilabel:`Username`: enter the server login username." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:188 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 msgid ":guilabel:`Password`: enter the server login password." msgstr "" @@ -14781,32 +16364,32 @@ msgstr "" msgid "Incoming email server configuration for Chilean DTE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:195 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:191 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:201 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:197 #: ../../content/applications/finance/fiscal_localizations/peru.rst:219 msgid "Certificate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:199 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:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:207 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 msgid ":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select the `.pfx` file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:204 msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:209 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:205 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)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:212 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 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." msgstr "" @@ -14814,59 +16397,59 @@ msgstr "" msgid "Digital certificate configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:220 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:216 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 #: ../../content/applications/finance/fiscal_localizations/peru.rst:230 msgid "Multicurrency" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:222 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:218 msgid "The official currency rate is provided by `Chilean 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:230 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 #: ../../content/applications/finance/fiscal_localizations/france.rst:306 msgid "Partner information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:228 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:237 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 msgid ":guilabel:`Email`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 msgid ":guilabel:`Identification Number`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:239 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:235 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 msgid ":guilabel:`Taxpayer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 msgid ":guilabel:`Activity Description`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:242 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 msgid "In the :guilabel:`Electronic Invoicing` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:244 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 msgid ":guilabel:`DTE Email`: enter the sender's email address for the partner." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:245 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:241 msgid ":guilabel:`Delivery Guide Price`: select which price the delivery guide displays, if any." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:248 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:244 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." msgstr "" @@ -14874,11 +16457,11 @@ msgstr "" msgid "Chilean electronic invoice data for partners." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:258 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 msgid "Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos Internos)`-defined document types." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:261 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:257 msgid "Document types are created automatically upon installation of the localization module, and can be managed by navigating to :menuselection:`Accounting --> Configuration --> Document Types`." msgstr "" @@ -14886,166 +16469,166 @@ msgstr "" msgid "Chilean fiscal document types list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:265 msgid "Several document types are inactive by default but can be activated by toggling the :guilabel:`Active` option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:275 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 msgid "The document type on each transaction is determined by:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:277 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 msgid "The journal related to the invoice, identifying if the journal uses documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:278 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:274 msgid "The condition applied based on the type of issuer and recipient (e.g., the buyer or vendor's fiscal regime)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:284 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:280 msgid "*Sales journals* in Odoo usually represent a business unit or location." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:287 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:283 msgid "Ventas Santiago." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:288 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:284 msgid "Ventas Valparaiso." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 msgid "For retail stores it is common to have one journal per :abbr:`POS (Point of Sale)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:293 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:289 msgid "Cashier 1." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:294 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 msgid "Cashier 2." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:296 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:301 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:297 msgid "Tax payments to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:302 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:298 msgid "Employees payments." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:305 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:301 msgid "Create a sales journal" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:307 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:303 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:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:310 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:306 msgid ":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for customer invoice journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:311 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:307 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:311 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:319 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 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 `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:326 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:322 msgid "CAF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:328 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:324 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:333 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:329 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:338 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:334 msgid "Please refer to the `SII documentation `_ to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` files." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:342 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:338 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:347 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:343 msgid "Upload CAF files" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:349 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:345 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:356 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:352 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:360 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:356 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:367 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:363 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:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:371 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:367 msgid "Default Account Payable" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:372 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 #: ../../content/applications/finance/fiscal_localizations/peru.rst:75 msgid "Default Account Receivable" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:373 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:369 msgid "Transfer Accounts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:374 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 msgid "Conversion Rate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:382 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:378 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:386 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:382 msgid "Chile has several tax types, the most common ones are:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:388 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:384 msgid "**VAT**: the regular VAT can have several rates." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:389 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:385 msgid "**ILA**: the tax for alcoholic drinks." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:392 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:388 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 #: ../../content/applications/finance/fiscal_localizations/romania.rst:106 msgid ":doc:`../accounting/taxes`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:398 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:394 msgid "Electronic invoice workflow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:400 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:396 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." msgstr "" @@ -15053,11 +16636,11 @@ msgstr "" msgid "Diagram with Electronic invoice transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:409 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:405 msgid "Customer invoice emission" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:411 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:407 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`." msgstr "" @@ -15065,24 +16648,24 @@ msgstr "" msgid "Customer invoice document type selection." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:421 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:417 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:427 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:879 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:423 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 msgid "Validation and DTE status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:429 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:425 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:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:432 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:428 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file is created automatically and recorded in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:434 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." msgstr "" @@ -15090,7 +16673,7 @@ msgstr "" msgid "DTE XML File displayed in chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:441 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:437 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:" msgstr "" @@ -15098,11 +16681,11 @@ msgstr "" msgid "Transition of DTE status flow." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:450 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:446 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:455 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:451 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`." msgstr "" @@ -15110,7 +16693,7 @@ msgstr "" msgid "Identification transaction for invoice and Status update." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:465 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:461 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." msgstr "" @@ -15118,35 +16701,35 @@ msgstr "" msgid "Electronic invoice data statuses." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:473 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:469 msgid "The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can take on one of these values:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:476 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:472 msgid ":guilabel:`Accepted`: indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:478 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:481 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:477 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:486 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:482 msgid "If the invoice is rejected please follow these steps:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:488 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 msgid "Change the document to :guilabel:`Draft`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:489 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:485 msgid "Make the required corrections based on the message received from the :abbr:`SII (Servicio de Impuestos Internos)` in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:491 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:487 msgid "Post the invoice again." msgstr "" @@ -15154,11 +16737,11 @@ msgstr "" msgid "Message when an invoice is rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:498 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:494 msgid "Crossed references" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:500 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 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." msgstr "" @@ -15166,14 +16749,14 @@ msgstr "" msgid "Crossed referenced document(s)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:512 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:508 #: ../../content/applications/finance/fiscal_localizations/india.rst:133 #: ../../content/applications/finance/fiscal_localizations/india.rst:271 #: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Invoice PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:514 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:510 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." msgstr "" @@ -15181,31 +16764,31 @@ msgstr "" msgid "SII Validation fiscal elements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:523 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:519 msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the `pdf417gen `_ library. Use the following command to install it: :command:`pip install pdf417gen`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 msgid "Commercial validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:533 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:534 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 msgid "Subsequently, if commercial terms and invoice data are correct, an acceptance confirmation is sent; otherwise, a claim is sent." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:536 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." msgstr "" @@ -15213,11 +16796,11 @@ msgstr "" msgid "Message with the commercial acceptance from the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:543 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 msgid "Processed for claimed invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:545 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 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." msgstr "" @@ -15225,12 +16808,12 @@ msgstr "" msgid "Invoice Commercial status updated to claimed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:555 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:551 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 msgid "Common errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:557 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 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:" msgstr "" @@ -15290,27 +16873,27 @@ msgstr "" msgid "**Hint:** there are just five reasons why this error could show up and all of them are related to the *Caratula* section of the XML:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 msgid "The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:590 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 msgid "The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:591 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:593 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 msgid "The resolution date is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:594 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:590 msgid "The resolution number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:601 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 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 ` for more information on the process to load the :abbr:`CAF (Folio Authorization Code)` on each document type." msgstr "" @@ -15318,16 +16901,16 @@ msgstr "" msgid "Creation of CAF for Credit notes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:613 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:669 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:609 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 msgid "Use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:616 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 msgid "Cancel referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:618 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 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`." msgstr "" @@ -15335,11 +16918,11 @@ msgstr "" msgid "Credit note canceling the referenced document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:628 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 msgid "Correct referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:630 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 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`." msgstr "" @@ -15347,7 +16930,7 @@ msgstr "" msgid "Credit note correcting referenced document text." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:639 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:635 msgid "Odoo creates a credit note with the corrected text in an invoice and :guilabel:`Price` `0.00`." msgstr "" @@ -15355,15 +16938,15 @@ msgstr "" msgid "Credit note with the corrected value on the invoice lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:642 msgid "Make sure to define the :guilabel:`Default Credit Account` in the sales journal specifically for this use case." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:650 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 msgid "Corrects referenced document amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:652 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 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`." msgstr "" @@ -15371,20 +16954,20 @@ msgstr "" msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:661 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Debit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:663 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:672 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 msgid "Add debt on invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:674 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 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." msgstr "" @@ -15392,7 +16975,7 @@ msgstr "" msgid "Debit note correcting referenced document amount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:682 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:678 msgid "In this case Odoo automatically includes the :guilabel:`Source Invoice` in the :guilabel:`Cross Reference` tab." msgstr "" @@ -15400,15 +16983,15 @@ msgstr "" msgid "Automatic reference to invoice in a debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:690 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 msgid "You can only add debit notes to an invoice already accepted by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:693 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 msgid "Cancel credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:695 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 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." msgstr "" @@ -15416,47 +16999,47 @@ msgstr "" msgid "Debit note to cancel the referenced document (credit note)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:706 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 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:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:709 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 msgid "Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios Electrónicos)` and create the vendor bill based on this information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 msgid "Automatically send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:712 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 msgid "Accept or claim the document and send this status to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 msgid "Reception" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 msgid "As soon as the vendor email with the attached :abbr:`DTE (Documentos Tributarios Electrónicos)` is received:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:720 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 msgid "The vendor bill maps all the information included in the XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 msgid "An email is sent to the vendor with the reception acknowledgement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:722 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 msgid "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:725 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 msgid "Acceptation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:727 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 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." msgstr "" @@ -15464,11 +17047,11 @@ msgstr "" msgid "Button for accepting vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:736 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 msgid "Claim" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:738 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:734 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." msgstr "" @@ -15477,60 +17060,60 @@ msgid "Claim button in vendor bills to inform the vendor all the document is com "rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:748 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:744 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:753 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:755 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:760 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:760 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:768 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 msgid "Once all configurations have been made for :ref:`electronic invoices ` (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 ` to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:774 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 msgid ":guilabel:`From Sales Order`: delivery guide takes the product price from the sales order and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:787 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 msgid "Delivery guide from a sales process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:790 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:792 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 msgid "When a sales order is created and confirmed, a delivery order is generated. After validating the delivery order, the option to create a delivery guide is activated." msgstr "" @@ -15538,11 +17121,11 @@ msgstr "" msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:800 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, stating the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:803 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:799 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`" msgstr "" @@ -15550,20 +17133,20 @@ msgstr "" msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:810 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:818 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:814 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:820 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." msgstr "" @@ -15571,11 +17154,11 @@ msgstr "" msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:830 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" @@ -15583,27 +17166,27 @@ msgstr "" msgid "Printing Delivery Guide PDF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:837 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:833 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 `)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:843 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 msgid "Electronic receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:845 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:850 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:846 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:854 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:850 msgid "Once all configurations have been made for :ref:`electronic invoices ` (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 ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:860 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:856 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." msgstr "" @@ -15611,7 +17194,7 @@ msgstr "" msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:869 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 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:" msgstr "" @@ -15619,15 +17202,15 @@ msgstr "" msgid "Document type 39 for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:881 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" @@ -15635,35 +17218,35 @@ msgstr "" msgid "Electronic Receipts STE creation status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 msgid "Please refer to the :ref:`DTE Workflow ` for electronic invoices as the workflow for electronic receipt follows the same process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:904 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 msgid "Electronic export of goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:906 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 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`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:911 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:907 msgid ":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency with :guilabel:`Chile - Facturación Electrónica`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:914 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:910 msgid "Once all configurations have been made for :ref:`electronic invoices ` (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 ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:920 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:916 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:925 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:921 msgid "Contact configurations" msgstr "" @@ -15671,11 +17254,11 @@ msgstr "" msgid "Taxpayer Type needed for the Electronic Exports of Goods module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:932 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 msgid "Chilean customs" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:934 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 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." msgstr "" @@ -15683,11 +17266,11 @@ msgstr "" msgid "Chilean customs fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:942 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 msgid "PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:944 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 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." msgstr "" @@ -15695,11 +17278,11 @@ msgstr "" msgid "PDF report section for the Electronic Exports of Goods PDF Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:953 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 msgid "eCommerce electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:955 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 msgid "To install the :guilabel:`Chilean eCommerce` module, go to :menuselection:`Apps, search for the module by its technical name `l10n_cl_edi_website_sale`, and click the :guilabel:`Activate` button." msgstr "" @@ -15707,27 +17290,27 @@ msgstr "" msgid "l10n_cl eCommerce module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:958 msgid "This module enables the features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:964 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:960 msgid "Generate electronic documents from the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:961 msgid "Support for required fiscal fields in the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:966 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 msgid "Effectively let the final client decide the electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 msgid "Once all of the configurations are made for the Chilean :ref:`electronic invoice ` flow, the following configurations are required for the eCommerce flow to be integrated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:973 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 msgid "To configure your website to generate electronic documents during the sale process, go to :menuselection:`Website --> Configuration --> Settings --> Invoicing` and activate the :guilabel:`Automatic Invoice` feature. Activating this feature allows electronic documents to be automatically generated when an online payment is confirmed." msgstr "" @@ -15735,15 +17318,15 @@ msgstr "" msgid "Invoice Policy and Automatic Invoice configurations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:982 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:978 msgid "Since an online payment needs to be confirmed for the *automatic invoice* feature to generate the document, a payment provider must be configured for the related website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:986 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:982 msgid "Review the :doc:`../payment_providers` documentation for information on which payment providers are supported in Odoo, and how to configure them." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:989 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:985 msgid "It is also recommended to configure your products so they are able to be invoiced when an online payment is confirmed. To do so, go to :menuselection:`Website --> eCommerce --> Products` and select the product template of the desired product. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Ordered quantities`." msgstr "" @@ -15751,12 +17334,12 @@ msgstr "" msgid "Invoice Policy configuration in Products." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:999 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1085 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:995 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1081 msgid "Invoicing flows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1001 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:997 msgid "Clients from Chile will be able to select if they need an **invoice** or a **ballot** for their purchase with an extra step added during the checkout process." msgstr "" @@ -15764,7 +17347,7 @@ msgstr "" msgid "Option for EDI Documents for clients." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1008 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1004 msgid "If the customer selects the :guilabel:`Electronic Invoice` option, fiscal fields are required to be filled out, including the :guilabel:`Activity Description`, the :guilabel:`Identification Number` and their :guilabel:`DTE Email`." msgstr "" @@ -15772,23 +17355,23 @@ msgstr "" msgid "Fiscal fields required for an Invoice to be requested." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1016 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1012 msgid "If the client selects the :guilabel:`Electronic Receipts` option, they will be directed to the next step, and the electronic document will be generated for the *Consumidor Final Anónimo* contact." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1015 msgid "Clients from countries other than Chile, will have their electronic receipts automatically generated for them by Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1023 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 msgid "If a purchase through eCommerce requires an export, the customer will need to contact your company to generate an electronic export invoice (*document type 110*), which can be done from the *Accounting* app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1028 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1024 msgid "Point of Sale electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1030 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1026 msgid "To install the :guilabel:`Chilean Module for Point of Sale`, go to the :menuselection:`Apps` application on the main Odoo dashboard, search for the module by its technical name `l10n_cl_edi_pos`, and click the :guilabel:`Activate` button." msgstr "" @@ -15796,47 +17379,47 @@ msgstr "" msgid "l10n_cl POS EDI module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1038 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 msgid "This module enables the following features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1040 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1036 msgid "Generate electronic documents from the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1041 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1037 msgid "Support the required fiscal fields for contacts created in the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1038 msgid "Effectively lets the final client decide the type of electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1044 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1040 msgid "Print QR or 5-digit codes in tickets to access to electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1046 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 msgid "To configure contacts with the required fiscal information, review the :ref:`partner information ` section, or directly modify a contact. Navigate to :menuselection:`Point of Sale --> Session --> Customers --> Details`, and edit any of the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1049 msgid ":guilabel:`Identification Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1054 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1050 msgid ":guilabel:`Tax Payer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1055 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1051 msgid ":guilabel:`Type Giro`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1056 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 msgid ":guilabel:`DTE Email`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1057 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 msgid ":guilabel:`RUT`" msgstr "" @@ -15844,7 +17427,7 @@ msgstr "" msgid "Contact with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1063 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1059 msgid "To configure the products, navigate to :menuselection:`Point of Sale --> Products --> Products` and select a product record. In the :guilabel:`Sales` tab of the product form, it is necessary to mark the product as :guilabel:`Available for POS`, this makes the product available for sale in the *Point of Sale* app." msgstr "" @@ -15852,15 +17435,15 @@ msgstr "" msgid "Product with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1072 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 msgid "Optionally, the following features are available for configuration in the :menuselection:`Point of Sale --> Configuration --> Settings --> Bills & Receipts section`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1075 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1071 msgid ":guilabel:`Use QR code on ticket`: this feature enables a QR code to be printed on the user's receipt so they can easily request an invoice after their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1077 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 msgid ":guilabel:`Generate a code on ticket`: this feature enables a 5-digit code to be generated on the receipt, allowing the user to request an invoice through the customer portal" msgstr "" @@ -15868,15 +17451,15 @@ msgstr "" msgid "Configuration to generate QR or 5 digit codes on tickets." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1087 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 msgid "The following sections cover the invoicing flows for the *Point of Sale* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1090 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 msgid "Electronic receipts: anonymous end user" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1092 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1088 msgid "When making a purchase as an anonymous user that does not request an electronic invoice, Odoo automatically selects :guilabel:`Consumidor Final Anónimo` as the contact for the order and generates the electronic receipt." msgstr "" @@ -15884,15 +17467,15 @@ msgstr "" msgid "Automatic contact selection of an anonymous end consumer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1101 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 msgid "If the client requests a credit note due to a return of their purchase, the credit note should be made using the *Accounting* app. See the :doc:`credit notes and refunds <../accounting/customer_invoices/credit_notes>` documentation for detailed instructions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1106 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 msgid "Electronic receipts: specific customer" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1108 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1104 msgid "When specific user makes a purchase that does not request an electronic invoice, Odoo automatically selects the contact for the order as the :guilabel:`Consumidor Final Anónimo`, and allows you to select or create the required customer contact with their fiscal information for the receipt." msgstr "" @@ -15900,16 +17483,16 @@ msgstr "" msgid "Selection of contact for the receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1113 msgid "If the client requests a credit note because of a return of this type of purchase, the credit note and return process can be managed directly from the :abbr:`POS (Point of Sale)` session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1121 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 msgid "Electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1123 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1119 msgid "When clients request an electronic invoice, it is possible to select or create the required contact with their fiscal information. When the payment is being made, select the option :guilabel:`Invoice` to generate the document." msgstr "" @@ -15917,15 +17500,15 @@ msgstr "" msgid "Selection of invoice option at payment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1128 msgid "For both the electronic receipts and invoices, if the product is not affected by taxes, Odoo detects this and generates the correct type of document for tax-exempt sales." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1136 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 msgid "Returns" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1138 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1134 msgid "For electronic receipts (not generated for the *Consumidor Final Anónimo*) and electronic invoices, it is possible to manage the process to return products sold in a :abbr:`POS (Point of Sale)` order by selecting the :guilabel:`Refund` button." msgstr "" @@ -15933,7 +17516,7 @@ msgstr "" msgid "Refund option in the POS application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1146 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1142 msgid "Orders can be searched by the order status or by contact, and be selected for the refund to be based on the client's original order." msgstr "" @@ -15941,23 +17524,23 @@ msgstr "" msgid "Selection of order for the refund process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1149 msgid "When the return payment is validated, Odoo generates the necessary credit note, referencing the original receipt or invoice, partially or fully canceling the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1157 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 msgid "`Smart tutorial - Electronic invoicing for point of sale `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1164 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1160 msgid "Balance tributario de 8 columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1170 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 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)`." msgstr "" @@ -15969,19 +17552,19 @@ msgstr "" msgid "Chilean Fiscal Balance (8 Columns)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1183 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1179 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1185 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 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." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1190 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1186 msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the :abbr:`SII (Servicio de Impuestos Internos)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1193 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1189 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." msgstr "" @@ -15989,7 +17572,7 @@ msgstr "" msgid "Location of the Propuesta F29 (CL) Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1200 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1196 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`." msgstr "" @@ -15997,7 +17580,7 @@ msgstr "" msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1208 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1204 msgid "Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." msgstr "" @@ -17508,8 +19091,8 @@ msgstr "" #: ../../content/applications/finance/payment_providers/asiapay.rst:34 #: ../../content/applications/finance/payment_providers/buckaroo.rst:27 #: ../../content/applications/finance/payment_providers/flutterwave.rst:29 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:27 -#: ../../content/applications/finance/payment_providers/razorpay.rst:29 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:30 +#: ../../content/applications/finance/payment_providers/razorpay.rst:37 msgid "Configuration on Odoo" msgstr "" @@ -18718,7 +20301,6 @@ msgid "The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can msgstr "" #: ../../content/applications/finance/fiscal_localizations/germany.rst:12 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:17 msgid "Be careful, you can only change the accounting package as long as you have not created any accounting entry." msgstr "" @@ -22932,7 +24514,7 @@ msgid "This generates the `Form_2307.xls` file that lists all the vendor bill li msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:81 -msgid "The same process above can also be done for a *single* vendor :doc:`payment <../accounting/payments>` if they were linked to one or more :doc:`vendor bills <../accounting/payments/multiple>` with applied withholding taxes." +msgid "The same process above can also be done for a *single* vendor :doc:`payment <../accounting/payments>` if they were linked to one or more :doc:`vendor bills <../accounting/payments>` with applied withholding taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:86 @@ -23349,11 +24931,11 @@ msgid "Spain" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:6 -msgid "Spanish Chart of Accounts" +msgid "Spanish chart of accounts" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:8 -msgid "In Odoo, there are several Spanish Chart of Accounts that are available by default:" +msgid "Several Spanish charts of accounts are available by default in Odoo:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:10 @@ -23369,33 +24951,49 @@ msgid "PGCE Entitades" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:14 -msgid "You can choose the one you want by going in :menuselection:`Accounting --> Configuration` then choose the package you want in the **Fiscal Localization** section." +msgid "To choose the one you want, go to :menuselection:`Accounting --> Configuration --> Settings`, then select a package in the :guilabel:`Fiscal localization` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:20 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:18 msgid "When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed by default." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:23 -msgid "Spanish Accounting Reports" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:21 +msgid "You can only change the accounting package as long as you have not created any accounting entry." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:25 -msgid "If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:24 +msgid "Spanish accounting reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:28 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:26 +msgid "If the Spanish accounting localization is installed, you have access to accounting reports specific to Spain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:30 msgid "Tax Report (Modelo 111)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:31 msgid "Tax Report (Modelo 115)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:30 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:32 msgid "Tax Report (Modelo 303)" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:33 +msgid "Tax Report (Modelo 347)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:34 +msgid "Tax Report (Modelo 349)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:35 +msgid "Tax Report (Modelo 390)" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:3 msgid "Switzerland" msgstr "" @@ -23546,17 +25144,6 @@ msgstr "" msgid "TVA 7.7%" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 -msgid "Purchases" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 @@ -24123,10 +25710,6 @@ msgstr "" msgid "By default, the UAE Central Bank exchange rates web service is used. Several other providers are available under the :guilabel:`Service` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 -msgid "Payroll" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:152 msgid "The :guilabel:`UAE - Payroll` module creates the necessary **salary rules** in the Payroll app in compliance with the UAE rules and regulations. The salary rules are linked to the corresponding accounts in the **chart of accounts**." msgstr "" @@ -24466,6 +26049,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers.rst:73 #: ../../content/applications/finance/payment_providers.rst:91 +#: ../../content/applications/finance/payment_providers.rst:127 #: ../../content/applications/finance/payment_providers.rst:139 msgid "Odoo" msgstr "" @@ -24473,6 +26057,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers.rst:74 #: ../../content/applications/finance/payment_providers.rst:92 #: ../../content/applications/finance/payment_providers.rst:104 +#: ../../content/applications/finance/payment_providers.rst:128 #: ../../content/applications/finance/payment_providers.rst:140 #: ../../content/applications/finance/payment_providers.rst:143 msgid "|V|" @@ -24496,7 +26081,6 @@ msgstr "" #: ../../content/applications/finance/payment_providers.rst:109 #: ../../content/applications/finance/payment_providers.rst:115 #: ../../content/applications/finance/payment_providers.rst:121 -#: ../../content/applications/finance/payment_providers.rst:127 #: ../../content/applications/finance/payment_providers.rst:133 msgid "The provider website" msgstr "" @@ -24902,10 +26486,10 @@ msgstr "" #: ../../content/applications/finance/payment_providers/authorize.rst:51 #: ../../content/applications/finance/payment_providers/buckaroo.rst:37 #: ../../content/applications/finance/payment_providers/flutterwave.rst:44 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:39 #: ../../content/applications/finance/payment_providers/mollie.rst:31 #: ../../content/applications/finance/payment_providers/paypal.rst:121 -#: ../../content/applications/finance/payment_providers/razorpay.rst:46 +#: ../../content/applications/finance/payment_providers/razorpay.rst:54 #: ../../content/applications/finance/payment_providers/sips.rst:32 #: ../../content/applications/finance/payment_providers/stripe.rst:133 msgid ":doc:`../payment_providers`" @@ -25203,8 +26787,8 @@ msgstr "" #: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:44 #: ../../content/applications/finance/payment_providers/asiapay.rst:47 #: ../../content/applications/finance/payment_providers/flutterwave.rst:36 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:33 -#: ../../content/applications/finance/payment_providers/razorpay.rst:36 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 +#: ../../content/applications/finance/payment_providers/razorpay.rst:44 msgid "Configure the rest of the options to your liking." msgstr "" @@ -25648,12 +27232,20 @@ msgstr "" 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`." msgstr "" -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:29 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:-1 +msgid "Production and testing credentials in Mercado Pago." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:32 msgid ":ref:`Navigate to the payment provider Mercado Pago ` and change its state to :guilabel:`Enabled`." msgstr "" -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:31 -msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` with the value you saved at the step :ref:`payment_providers/mercado_pago/configure_dashboard`." +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:34 +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." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:40 +msgid "`Mercado Pago Odoo webinar `_" msgstr "" #: ../../content/applications/finance/payment_providers/mollie.rst:3 @@ -25973,23 +27565,27 @@ msgstr "" msgid "Click on :guilabel:`Create Webhook` to finalize the configuration." msgstr "" -#: ../../content/applications/finance/payment_providers/razorpay.rst:31 +#: ../../content/applications/finance/payment_providers/razorpay.rst:29 +msgid "The :guilabel:`Recurring payments` feature must be activated if you want to make recurring payments. Send a request to the `Razorpay Support team `_ to enable recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:39 msgid ":ref:`Navigate to the payment provider Razorpay ` and change its state to :guilabel:`Enabled`." msgstr "" -#: ../../content/applications/finance/payment_providers/razorpay.rst:33 +#: ../../content/applications/finance/payment_providers/razorpay.rst:41 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`." msgstr "" -#: ../../content/applications/finance/payment_providers/razorpay.rst:39 +#: ../../content/applications/finance/payment_providers/razorpay.rst:47 msgid "If you configure Odoo to capture amounts manually:" msgstr "" -#: ../../content/applications/finance/payment_providers/razorpay.rst:41 +#: ../../content/applications/finance/payment_providers/razorpay.rst:49 msgid "Be aware that the **manual voiding** of a transaction is not supported by Razorpay." msgstr "" -#: ../../content/applications/finance/payment_providers/razorpay.rst:42 +#: ../../content/applications/finance/payment_providers/razorpay.rst:50 msgid "After **five days**, if the transaction hasn't been captured yet, it'll automatically be **voided**." msgstr "" @@ -26429,75 +28025,83 @@ msgid "Signature status" msgstr "" #: ../../content/applications/finance/sign.rst:104 +msgid "Validity dates and reminders" +msgstr "" + +#: ../../content/applications/finance/sign.rst:106 +msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields." +msgstr "" + +#: ../../content/applications/finance/sign.rst:112 #: ../../content/applications/finance/spreadsheet/templates.rst:3 msgid "Templates" msgstr "" -#: ../../content/applications/finance/sign.rst:106 +#: ../../content/applications/finance/sign.rst:114 msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/finance/sign.rst:111 +#: ../../content/applications/finance/sign.rst:119 msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." msgstr "" -#: ../../content/applications/finance/sign.rst:117 +#: ../../content/applications/finance/sign.rst:125 msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." msgstr "" -#: ../../content/applications/finance/sign.rst:122 -msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on ⋮, then :guilabel:`Template`. Click on ⋮ again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." +#: ../../content/applications/finance/sign.rst:130 +msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." msgstr "" -#: ../../content/applications/finance/sign.rst:130 +#: ../../content/applications/finance/sign.rst:139 msgid "Roles" msgstr "" -#: ../../content/applications/finance/sign.rst:132 +#: ../../content/applications/finance/sign.rst:141 msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." msgstr "" -#: ../../content/applications/finance/sign.rst:136 +#: ../../content/applications/finance/sign.rst:145 msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." msgstr "" -#: ../../content/applications/finance/sign.rst:138 +#: ../../content/applications/finance/sign.rst:147 msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." msgstr "" -#: ../../content/applications/finance/sign.rst:146 +#: ../../content/applications/finance/sign.rst:155 msgid "Secured identification" msgstr "" -#: ../../content/applications/finance/sign.rst:148 +#: ../../content/applications/finance/sign.rst:157 msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`Itsme® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." msgstr "" -#: ../../content/applications/finance/sign.rst:154 +#: ../../content/applications/finance/sign.rst:163 msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" msgstr "" -#: ../../content/applications/finance/sign.rst:155 +#: ../../content/applications/finance/sign.rst:164 msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/finance/sign.rst:160 +#: ../../content/applications/finance/sign.rst:169 msgid "SMS verification" msgstr "" -#: ../../content/applications/finance/sign.rst:162 +#: ../../content/applications/finance/sign.rst:171 msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." msgstr "" -#: ../../content/applications/finance/sign.rst:166 +#: ../../content/applications/finance/sign.rst:175 msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." msgstr "" -#: ../../content/applications/finance/sign.rst:170 +#: ../../content/applications/finance/sign.rst:179 msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." msgstr "" -#: ../../content/applications/finance/sign.rst:174 +#: ../../content/applications/finance/sign.rst:183 msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." msgstr "" @@ -26505,27 +28109,27 @@ msgstr "" msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/finance/sign.rst:182 +#: ../../content/applications/finance/sign.rst:191 msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/finance/sign.rst:183 +#: ../../content/applications/finance/sign.rst:192 msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." msgstr "" -#: ../../content/applications/finance/sign.rst:189 +#: ../../content/applications/finance/sign.rst:198 msgid "Itsme®" msgstr "" -#: ../../content/applications/finance/sign.rst:191 +#: ../../content/applications/finance/sign.rst:200 msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**." msgstr "" -#: ../../content/applications/finance/sign.rst:194 +#: ../../content/applications/finance/sign.rst:203 msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`." msgstr "" -#: ../../content/applications/finance/sign.rst:199 +#: ../../content/applications/finance/sign.rst:208 msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." msgstr "" @@ -26533,19 +28137,19 @@ msgstr "" msgid "select customer identified with itsme®" msgstr "" -#: ../../content/applications/finance/sign.rst:205 +#: ../../content/applications/finance/sign.rst:214 msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required." msgstr "" -#: ../../content/applications/finance/sign.rst:210 +#: ../../content/applications/finance/sign.rst:219 msgid "Signatory hash" msgstr "" -#: ../../content/applications/finance/sign.rst:212 +#: ../../content/applications/finance/sign.rst:221 msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." msgstr "" -#: ../../content/applications/finance/sign.rst:217 +#: ../../content/applications/finance/sign.rst:226 msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." msgstr "" @@ -26553,103 +28157,103 @@ msgstr "" msgid "Adding the visual security frame to a signature." msgstr "" -#: ../../content/applications/finance/sign.rst:229 -msgid "Tags can be used to categorize and organize documents, allowing users to search for and filter documents based on specific criteria quickly." +#: ../../content/applications/finance/sign.rst:238 +msgid "Tags can be used to categorize and organize documents, allowing users to quickly search for and filter documents based on specific criteria." msgstr "" -#: ../../content/applications/finance/sign.rst:232 +#: ../../content/applications/finance/sign.rst:241 msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." msgstr "" -#: ../../content/applications/finance/sign.rst:236 +#: ../../content/applications/finance/sign.rst:245 msgid "To apply a tag to a document, use the dropdown list available in your document." msgstr "" -#: ../../content/applications/finance/sign.rst:239 -msgid "Sign order" +#: ../../content/applications/finance/sign.rst:248 +msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`." msgstr "" -#: ../../content/applications/finance/sign.rst:241 -msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." +#: ../../content/applications/finance/sign.rst:253 +msgid "Sign order" msgstr "" -#: ../../content/applications/finance/sign.rst:244 -msgid "By going to :menuselection:`Configuration --> Settings`, you can :guilabel:`Enable Signing Order`. Each recipient receives the signature request notification only once the previous recipient has completed their action." +#: ../../content/applications/finance/sign.rst:255 +msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." msgstr "" -#: ../../content/applications/finance/sign.rst:248 -msgid "Add at least two :guilabel:`Signature` fields with different roles to your document. Click :guilabel:`Send`, go to the :guilabel:`Options` tab, and tick the :guilabel:`Specify signing order` box." +#: ../../content/applications/finance/sign.rst:258 +msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." msgstr "" -#: ../../content/applications/finance/sign.rst:252 -msgid "Add the signer's :guilabel:`Name or email` information. You can decide on the :guilabel:`Sign Order` by typing :guilabel:`1` or :guilabel:`2` in the :guilabel:`Sign Order` column." +#: ../../content/applications/finance/sign.rst:263 +msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action." msgstr "" -#: ../../content/applications/finance/sign.rst:256 +#: ../../content/applications/finance/sign.rst:267 msgid "`Odoo Quick Tips: Sign order [video] `_" msgstr "" -#: ../../content/applications/finance/sign.rst:261 +#: ../../content/applications/finance/sign.rst:272 msgid "Field types" msgstr "" -#: ../../content/applications/finance/sign.rst:263 +#: ../../content/applications/finance/sign.rst:274 msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." msgstr "" -#: ../../content/applications/finance/sign.rst:267 +#: ../../content/applications/finance/sign.rst:278 msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." msgstr "" -#: ../../content/applications/finance/sign.rst:271 +#: ../../content/applications/finance/sign.rst:282 msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/finance/sign.rst:274 +#: ../../content/applications/finance/sign.rst:285 msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" msgstr "" -#: ../../content/applications/finance/sign.rst:277 +#: ../../content/applications/finance/sign.rst:288 msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." msgstr "" -#: ../../content/applications/finance/sign.rst:280 +#: ../../content/applications/finance/sign.rst:291 msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." msgstr "" -#: ../../content/applications/finance/sign.rst:282 +#: ../../content/applications/finance/sign.rst:293 msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/finance/sign.rst:283 +#: ../../content/applications/finance/sign.rst:294 msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/finance/sign.rst:284 +#: ../../content/applications/finance/sign.rst:295 msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/finance/sign.rst:285 +#: ../../content/applications/finance/sign.rst:296 msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/finance/sign.rst:287 +#: ../../content/applications/finance/sign.rst:298 msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." msgstr "" -#: ../../content/applications/finance/sign.rst:292 +#: ../../content/applications/finance/sign.rst:303 msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." msgstr "" -#: ../../content/applications/finance/sign.rst:296 +#: ../../content/applications/finance/sign.rst:307 msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/finance/sign.rst:299 +#: ../../content/applications/finance/sign.rst:310 msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height." msgstr "" -#: ../../content/applications/finance/sign.rst:305 +#: ../../content/applications/finance/sign.rst:316 msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index fdf25861ad..7125478b7e 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 2f17d612f4..d13ddd828f 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,2217 +20,5533 @@ msgstr "" msgid "Human resources" msgstr "" -#: ../../content/applications/hr/attendances.rst:8 +#: ../../content/applications/hr/attendances.rst:5 msgid "Attendances" msgstr "" -#: ../../content/applications/hr/attendances.rst:10 -msgid "**Odoo Attendances** functions as a time clock. Employees check in and check out of work, while managers can see who is available at any given time." +#: ../../content/applications/hr/attendances.rst:12 +msgid "Odoo's *Attendances* application functions as a time clock. Employees are able to check in and out of work using a dedicated device in kiosk mode, while users are also able to check in and out of work directly from the database. Managers can quickly see who is available at any given time, and create reports to see everyone's hours, and gain insights on which employees are working overtime, or checking out of work earlier than expected." msgstr "" -#: ../../content/applications/hr/attendances.rst:14 -msgid "`Odoo Tutorials: Attendances `_" +#: ../../content/applications/hr/attendances.rst:21 +msgid "Access Rights" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:3 -msgid "Hardware" +#: ../../content/applications/hr/attendances.rst:23 +msgid "It is important to understand how the different access rights affect what users can access in the *Attendances* application." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:6 -msgid "Kiosk management" +#: ../../content/applications/hr/attendances.rst:26 +msgid "Every user in the database is always able to access their own information on the dashboard, and can check in and out directly from the database. Access to all the other features is determined by access rights." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:8 -msgid "A kiosk is a self-service station that allows employees to check in and check out for work shifts." +#: ../../content/applications/hr/attendances.rst:30 +msgid "To see what access rights a user has, navigate to the :menuselection:`Settings application --> Users & Companies: Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`Human Resources` section to see the setting. For the :guilabel:`Attendances` field, the options are either to leave the field blank, or select :guilabel:`Administrator`." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:10 -msgid "There are two ways to set up a kiosk:" +#: ../../content/applications/hr/attendances.rst:36 +msgid "If the :guilabel:`Administrator` option is selected, the user has full access to the entire *Attendances* application, with no restrictions. They can view all employee attendance records, enter kiosk mode from the application, access all reporting metrics, and make modifications to the settings." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:12 -msgid "**Laptop and desktop PC**" +#: ../../content/applications/hr/attendances.rst:41 +msgid "If left blank, the user can only view their own information on the *Attendances* application dashboard, and can view their own personal attendance records under the reporting feature. Everyone else's attendance records will be hidden from view on the report. There is no access to either the kiosk mode or the configuration menu." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:14 -msgid "Running a kiosk in a web browser is the cheapest and most flexible option. You can print employee badges with any thermal or inkjet printer compatible with your web browser." +#: ../../content/applications/hr/attendances.rst:49 +msgid "Approvers" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:17 -msgid "**Tablet and mobile phone (Android or iOS)**" +#: ../../content/applications/hr/attendances.rst:51 +msgid "The only other scenario where different information may be accessible in the *Attendances* application is for approvers. If a user does *not* have administrative rights for the *Attendances* application, but they are set as an employee's approver for the *Attendances* application, that user will be able to view the attendance records for that specific employee, as well as make modifications to that employee's attendance records (when necessary). This applies to all employee's the user is listed as the *Attendances* application approver. Approvers are typically managers, though this is not necessary." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:19 -msgid "Tablets and mobile phones take up much less space, and their touchscreens are easy to use. Consider putting them in a secure stand at the front desk or mounting them securely on a wall." +#: ../../content/applications/hr/attendances.rst:59 +msgid "To see who the attendance approver is for an employee, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, and scroll to the :guilabel:`Approvers` section, and check the :guilabel:`Attendance` field. The person selected will be able to view that employees' attendance records, both on the *Attendances* application dashboard as well as in the attendance reports, and make modifications to their records." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:23 -msgid "We recommend using an iPad together with the `Heckler Design WindFall Stand `_" +#: ../../content/applications/hr/attendances.rst:67 +msgid "Configuration" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:27 -msgid "RFID key fob readers" +#: ../../content/applications/hr/attendances.rst:69 +msgid "There are very few configurations needed in the *Attendances* application. Determining how employees check in and out, defining how the kiosks function, and determining how extra hours are computed are all set in the Configuration menu. Navigate to the :menuselection:`Attendances application--> Configuration` to access the configuration menu." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:29 -msgid "Employees can scan personal RFID key fobs with an RFID reader to manage check-ins and check-outs quickly and easily." +#: ../../content/applications/hr/attendances.rst:75 +msgid "Modes" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:-1 -msgid "An RFID key fob is placed on an RFID reader" +#: ../../content/applications/hr/attendances.rst:79 +msgid ":guilabel:`Kiosk Mode`: using the drop-down menu, select how an employee checks in when using a kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual Selection`." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:38 -msgid "We recommend using the `Neuftech USB RFID Reader `_." +#: ../../content/applications/hr/attendances.rst:84 +msgid "The *Barcode* application **does not** need to be installed in order to use one of the Barcode/RFID settings." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:41 -#: ../../content/applications/hr/attendances/hardware.rst:57 -msgid "An IoT box is **not** required." +#: ../../content/applications/hr/attendances.rst:87 +msgid ":guilabel:`Attendances from Backend`: activate this selection to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:44 -msgid "Barcode scanners" +#: ../../content/applications/hr/attendances.rst:94 +msgid "Kiosk Settings" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:46 -msgid "Employees can scan the barcode on their employee badges to manage check-ins and check-outs quickly and easily. The kiosk mode works with most USB barcode scanners connected directly to a computer. Bluetooth barcode scanners are also supported natively." +#: ../../content/applications/hr/attendances.rst:96 +msgid "This section only needs to be configured if employees use kiosks for checking in and out. If kiosks are *not* being used, modifying any of these fields will **not** adversely affect the functionality of the Attendances application." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:51 -msgid "We recommend using the `Honeywell product line `_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout." +#: ../../content/applications/hr/attendances.rst:100 +msgid ":guilabel:`Barcode Source`: this setting appears if either of the two Barcode/RFID selections were configured for the :ref:`Kiosk Mode ` setting. Select how barcodes are scanned at the kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's :guilabel:`Front Camera`, or :guilabel:`Back Camera`." msgstr "" -#: ../../content/applications/hr/employees.rst:7 -msgid "Employees" +#: ../../content/applications/hr/attendances.rst:104 +msgid ":guilabel:`Employee PIN Identification`: activate this option if employees should use a unique PIN to check in. PINs are configured on each individual employee record. Refer to the :doc:`../hr/employees/new_employee` documentation for more information on setting up PINs." msgstr "" -#: ../../content/applications/hr/employees.rst:9 -msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments." +#: ../../content/applications/hr/attendances.rst:107 +msgid ":guilabel:`Display Time`: set the duration (in seconds) the check in and check out confirmation screen remains on the kiosk before going back to the main check in screen." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:3 -msgid "Add a new employee" +#: ../../content/applications/hr/attendances.rst:109 +msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) in order to use a device as a kiosk without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the Attendances application kiosk." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:5 -msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`Create` button to create a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." +#: ../../content/applications/hr/attendances.rst:114 +msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the Attendances application kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL and update the kiosk(s) accordingly." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Create a new employee card." +#: ../../content/applications/hr/attendances.rst:120 +msgid "Extra Hours" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:15 -msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields." +#: ../../content/applications/hr/attendances.rst:122 +msgid ":guilabel:`Count of Extra Hours`: enable this box to allow employees to log extra hours beyond their set working hours (sometimes referred to as *overtime*). Activating this selection displays the following settings as well. If this is not activated, no other configurations appear." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:19 -msgid "General information" +#: ../../content/applications/hr/attendances.rst:126 +msgid ":guilabel:`Start From`: the current date is automatically entered in this field. If desired, click on this field and use the calendar selector to modify the start date that extra hours will be logged." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:22 -#: ../../content/applications/hr/payroll/contracts.rst:39 -#: ../../content/applications/hr/payroll/payslips.rst:51 -msgid "Required fields" +#: ../../content/applications/hr/attendances.rst:129 +msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that will *not* count towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time will *not* be counted as overtime for the employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:24 -msgid ":guilabel:`Name`: Enter the employee's name." +#: ../../content/applications/hr/attendances.rst:133 +msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that will not adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours, and less than this specified grace period, they will not be penalized for their reduced hours." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:25 -msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." +#: ../../content/applications/hr/attendances.rst:138 +msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:33 -#: ../../content/applications/hr/payroll/contracts.rst:66 -#: ../../content/applications/hr/payroll/payslips.rst:91 -msgid "Optional fields" +#: ../../content/applications/hr/attendances.rst:142 +msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company is set from 9:00 AM to 5:00 PM. If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are *not* counted towards their overtime. If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they will not be penalized for this discrepancy." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:35 -msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." +#: ../../content/applications/hr/attendances.rst:150 +msgid "Check in and out via the database" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:37 -msgid ":guilabel:`Job Position`: Enter the employee's job position title." +#: ../../content/applications/hr/attendances.rst:152 +msgid "Odoo's *Attendances* application allows users who are logged into the database to check in and out, without needing to go into the *Attendances* application, or use a kiosk. For some smaller companies, where every employee is also a user, this feature may be useful." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:38 -msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added." +#: ../../content/applications/hr/attendances.rst:156 +msgid "A user can check in and out on the main database dashboard, as well as in any application. In the upper right corner of the top main menu, which is always visible regardless of what application the user is in, a :guilabel:`🔴 (red circle)` or :guilabel:`🟢 (green circle)` is visible. Click on the colored circle to reveal the attendance widget, enabling the user to check in and/or out." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:41 -msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "Top right main menu with check in button highlighted." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:43 -msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:166 +msgid "Check in" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:44 -msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:168 +msgid "If the attendance widget circle is red, this indicates the user is not currently checked in. Click the :guilabel:`🔴 (red circle)` and the attendance widget appears, displaying a green :guilabel:`Check in ->` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:45 -msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:176 +msgid "If the user has not checked in and out already during the current work day, this button is the only visible item in the widget. If the user has previously checked in and out, a :guilabel:`Total today` field appears above the button, and the total amount of time that has been logged for the day appears beneath that field, in an :guilabel:`XX:XX` (hours:minutes) format." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:48 -msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." +#: ../../content/applications/hr/attendances.rst:181 +msgid "Click the :guilabel:`Check in ->` button to check in. The :guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget changes appearance as well. The widget updates to reflect that the user has checked in, by changing the green :guilabel:`Check in ->` button to a yellow :guilabel:`Check out ->` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:52 -msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." +#: ../../content/applications/hr/attendances.rst:186 +msgid "Click anywhere on the screen to close the attendance widget." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:58 -msgid "Additional information tabs" +#: ../../content/applications/hr/attendances.rst:189 +msgid "Check out" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:61 -msgid "Resumé tab" +#: ../../content/applications/hr/attendances.rst:191 +msgid "If the user is checking out for the first time, :guilabel:`Since XX:XX (AM/PM)` appears at the top of the widget, with the time the user checked in populating the time field. Beneath that line, :guilabel:`XX:XX` is displayed, indicating the hours and minutes that have elapsed since checking in. As time passes, this value is updated to reflect the hours and minutes that have passed since the user checked in." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:64 -msgid "Resumé" +#: ../../content/applications/hr/attendances.rst:197 +msgid "If the user has previously checked in and out, additional fields are presented. A :guilabel:`Before XX:XX (AM/PM)` field appears in addition to the :guilabel:`Since XX:XX (AM/PM)` field. The time displayed in both of these fields are populated with the most recent check in time, and will match. Beneath the :guilabel:`Before XX:XX (AM/PM)` field, the previously logged hours are displayed, in an :guilabel:`XX:XX` (hours:minutes) format." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:66 -msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information for each entry." +#: ../../content/applications/hr/attendances.rst:203 +msgid "In addition, beneath both of these fields, a :guilabel:`Total today` field appears. This field is the sum of both the :guilabel:`Before XX:XX (AM/PM)` and :guilabel:`Since XX:XX (AM/PM)` fields, and is the total time that will be logged for the user, if they were to log out at that moment." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Add information for the previous work experience in this form." +#: ../../content/applications/hr/attendances.rst:207 +msgid "As time passes, both the :guilabel:`Since XX:XX (AM/PM)` and :guilabel:`Total today` fields are updated live. To check out, click the yellow :guilabel:`Check out ->` button. The attendance widget updates again, displaying the :guilabel:`Total today` field with the logged time, and the yellow :guilabel:`Check out ->` button changes to a green :guilabel:`Check in ->` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:74 -msgid ":guilabel:`Title`: Type in the title of the previous work experience." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The pop-up that appears when an employee checks in inside the database." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:75 -msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry." +#: ../../content/applications/hr/attendances.rst:217 +msgid "There is no limit to the amount of times a user can check in and check out. Users are able to check in and out without any time elapsing (a value of 00:00). Each time an employee logs in and out, the information is stored and appears on the dashboard, including check ins and check outs with no time value." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:78 -msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:223 +msgid "Kiosk Mode" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:80 -msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." +#: ../../content/applications/hr/attendances.rst:225 +msgid "Some companies may opt to use a dedicated device (a laptop or desktop PC, a tablet, or a mobile phone) for employees to check in and check out from. Kiosk mode is used for these scenarios." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:83 -msgid ":guilabel:`Description`: Enter any relevant details in the field." +#: ../../content/applications/hr/attendances.rst:229 +msgid "If users check in and out using either a badge or an RFID, then an accessible device in kiosk mode **must** be available in order to check in and check out using these two methods." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:85 -msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." +#: ../../content/applications/hr/attendances.rst:232 +msgid "Entering kiosk mode is only available for users with specific :ref:`access rights `." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:90 -msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab as :guilabel:`Experience`, with the end date listed as :guilabel:`Current`." +#: ../../content/applications/hr/attendances.rst:235 +msgid "There are three ways that kiosk mode can be activated:" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:95 -msgid "Skills" +#: ../../content/applications/hr/attendances.rst:237 +msgid "Navigate to the :guilabel:`Attendances` application, and click :guilabel:`Kiosk Mode` in the top menu. The device then enters kiosk mode." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:97 -msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information on the form." +#: ../../content/applications/hr/attendances.rst:239 +msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click on the link in the :guilabel:`Attendance Kiosk Url` field. A new tab opens in kiosk mode. It is recommended to close the database tab to keep the database secure." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Create a new skill for the employee." +#: ../../content/applications/hr/attendances.rst:243 +msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click :guilabel:`Copy` next to the link beneath the :guilabel:`Attendance Kiosk Url` field. Paste this URL into a web browser on the kiosk device and navigate to it." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:105 -msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The Attendances Kiosk URL field in the settings section of the Attendances application." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:107 -msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one." +#: ../../content/applications/hr/attendances.rst:252 +msgid "As a security measure, once a device is in kiosk mode, it is not possible to exit kiosk mode and go back into the database without singing back in. To exit kiosk mode, click the back button in the web browser. This logs the user out of the database, and returns to the main log in screen. This prevents anyone from accessing the database, adding another layer of security." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:111 -msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a skill level, then the progress bar automatically displays the pre-defined progress for that skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Level` field." +#: ../../content/applications/hr/attendances.rst:258 +msgid "Badge" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:117 -msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another skill." +#: ../../content/applications/hr/attendances.rst:260 +msgid "To check in or out using a badge, tap the :guilabel:`📷 (camera) Tap to scan` image in the center of the kiosk. Then, scan the barcode on the badge using the method configured in the :ref:`kiosk settings ` section of the configuration menu. Options are a dedicated barcode scanning device, or the kiosk's front or back camera. Once the barcode is scanned, the employee is checked in or out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:121 -msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:128 -msgid "Skill types" +#: ../../content/applications/hr/attendances.rst:272 +msgid "RFID" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:130 -msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`Create` and a new :guilabel:`Skill Type` form appears. Fill out all the details and then click :guilabel:`Save`. Repeat this for all the skill types needed." +#: ../../content/applications/hr/attendances.rst:274 +msgid "To check in or out using an RFID key fob, simply scan the fob with an RFID reader. Once scanned, the employee is then either checked in or checked out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:136 -msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This should be somewhat generic, since the specific skills listed will be housed under this category." +#: ../../content/applications/hr/attendances.rst:279 +msgid "Manually" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:138 -msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other needed skills." +#: ../../content/applications/hr/attendances.rst:281 +msgid "Users who do not have a scannable badge or an RFID fob can manually check in and out at a kiosk. Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen with all the employees that can be checked in or out appears. This is the same view as in the *Employees* application dashboard. Tap on the person, and they are either checked in or checked out, and a :ref:`confirmation message ` appears." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:140 -msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form." +#: ../../content/applications/hr/attendances.rst:287 +msgid "When a large number of employees appear in the list, making scrolling inefficient, there are two ways to quickly find a specific person:" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:146 -msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." +#: ../../content/applications/hr/attendances.rst:290 +msgid ":guilabel:`Search...`: tap on the :guilabel:`Search...` field and enter the person's name. As the name is typed in, the matching results are displayed on the screen." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:0 -msgid "Add new math skills and levels with the skill types form." +#: ../../content/applications/hr/attendances.rst:292 +msgid ":guilabel:`Department`: to quickly filter the presented employees, tap on a department to display only those employees that are part of that department. The :guilabel:`Departments` are listed on the left side of the screen, and the number at the end of each department indicates how many employees are part of the department, and will be displayed when selected." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:157 -msgid "Work information tab" +#: ../../content/applications/hr/attendances.rst:298 +msgid "PIN" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:159 -msgid "The :guilabel:`Work Information` tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Enter the following information for the new employee." +#: ../../content/applications/hr/attendances.rst:300 +msgid "If the :guilabel:`Employee PIN Identification` option was activated in the :ref:`kiosk settings ` section of the configuration menu, the employee is prompted to enter a PIN when manually checking in or out." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:164 -msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` and :guilabel:`Work Location` from the corresponding drop-down menus. The work address :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is the specific location details, such as a floor or building. If a new work location is needed, add the location by typing it in the field." +#: ../../content/applications/hr/attendances.rst:304 +msgid "After the employee is selected, a number pad appears with a message. When checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check in` appears above the numbers. When checking out, :guilabel:`(Employee) Want to check out? Please enter your PIN to check out` appears above the numbers." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:169 -msgid ":guilabel:`Approvers`: Using the drop-down menus, select the users responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." +#: ../../content/applications/hr/attendances.rst:309 +msgid "Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The employee is then checked in or out, and a :ref:`confirmation message ` appears." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:174 -msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` (both required) for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here. Click :guilabel:`Save` to save any changes." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:178 -msgid ":guilabel:`Planning`: The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." +#: ../../content/applications/hr/attendances.rst:319 +msgid "Confirmation message" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:0 -msgid "Add the work information to the Work Information tab." +#: ../../content/applications/hr/attendances.rst:321 +msgid "When an employee checks in or out, a confirmation message appears with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in. An :guilabel:`Hours Previously Today: XX:XX` field also appears, displaying any time already logged for that employee for the day. If no time has already been logged, the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` button. To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:191 -msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section must have *Administrator* rights set for the corresponding human resources role. To check who has these rights, go to :menuselection:`Settings app --> Users --> Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." +#: ../../content/applications/hr/attendances.rst:328 +msgid "When checking out, the screen displays a goodbye message, with the date and time of check out, and the total hours logged for the day. Beneath the message is a :guilabel:`Goodbye` button. To exit the screen before the preset time, tap the :guilabel:`Goodbye` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:196 -msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they must have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The goodbye message with all the employee's check out information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:199 -msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they must have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." +#: ../../content/applications/hr/attendances.rst:337 +msgid "Overview" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:201 -msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they must have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." +#: ../../content/applications/hr/attendances.rst:339 +msgid "When entering the *Attendances* application, the :guilabel:`Overview` dashboard is presented, containing all the check in and check out information for the signed in user. If the user has specific :ref:`access rights ` and/or are :ref:`approvers ` for specific employees, then those additional employee's check in and check out information is also visible on the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:206 -msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." +#: ../../content/applications/hr/attendances.rst:346 +msgid "Views" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:209 -msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." +#: ../../content/applications/hr/attendances.rst:348 +msgid "To change the view from the default Gantt chart to a list view, click the :guilabel:`List` icon in the top right of the dashboard, beneath the user's photo. To switch back to the Gantt chart, click the :guilabel:`Gantt` button, located next to the :guilabel:`List` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:212 -msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." +#: ../../content/applications/hr/attendances.rst:352 +msgid "The default view presents the current day's information. To present the information for the :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down, displaying those other options. Select the desired view, and the dashboard will update, presenting the selected information. To change the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click the left or right :guilabel:`arrow` buttons on either side of the drop-down button. To jump back to a view containing the current day, click the :guilabel:`Today` button. The refreshed the dashboard, presenting information containing the current day's information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:217 -msgid "After the new working time is created, set the working hours for the employee." +#: ../../content/applications/hr/attendances.rst:361 +msgid "In the :guilabel:`Day` view, the column for the current hour is highlighted in yellow. If the :guilabel:`Week` or :guilabel:`Month` view is selected, the column for the current day is highlighted. If the :guilabel:`Year` view is selected, the current month is highlighted." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:220 -msgid "Private information tab" +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The overview dashboard presenting the information for the week, with the current day\n" +"highlighted." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:222 -msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." +#: ../../content/applications/hr/attendances.rst:370 +msgid "Any entries that have errors appear in red, indicating they need to be resolved by a user with the proper :ref:`access rights ` and/or are :ref:`approvers ` for the employee(s) with the errors." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:227 -msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." +#: ../../content/applications/hr/attendances.rst:377 +msgid "Filters and Groups" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:232 -msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`" +#: ../../content/applications/hr/attendances.rst:379 +msgid "To filter the results in the dashboard or to present different groups of information, click the drop-down button in the :guilabel:`Search` bar above the dashboard, then select one of the available :guilabel:`Filters` or :guilabel:`Group By` options. There are several pre-configured filters and groups to choose from, as well as an option to create custom ones." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:238 -msgid "Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." +#: ../../content/applications/hr/attendances.rst:385 +msgid "Filters" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:241 -msgid "Next, enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the corresponding fields." +#: ../../content/applications/hr/attendances.rst:387 +msgid "The default filters that can be selected are:" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:244 -msgid "Select the employee's preferred :guilabel:`Language` from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:389 +msgid ":guilabel:`My Attendances`: this filter only presents the user's attendance data." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:246 -msgid "Enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. If the bank is not already configured (the typical situation when creating a new employee) enter the bank account number, and click :guilabel:`Create and Edit`. A :guilabel:`Create: Bank Account Number` for appears. Fill in the information, then click :guilabel:`Save`." +#: ../../content/applications/hr/attendances.rst:390 +msgid ":guilabel:`My Team`: this filter presents the attendance data for the user's team." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:251 -msgid "Finally, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits." +#: ../../content/applications/hr/attendances.rst:391 +msgid ":guilabel:`At Work`: this filter displays the attendance data for everyone currently checked in." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:254 -msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." +#: ../../content/applications/hr/attendances.rst:392 +msgid ":guilabel:`Errors`: this filter displays any entries with :ref:`errors ` that need to be resolved." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:257 -msgid ":guilabel:`Emergency`: Type in the name and phone number of the employee's emergency contact." +#: ../../content/applications/hr/attendances.rst:394 +msgid ":guilabel:`Check In`: this filter has a drop-down to further select a specific time period. Select the desired time period from the options presented, a specific month, quarter, or year." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:258 -msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." +#: ../../content/applications/hr/attendances.rst:396 +msgid ":guilabel:`Last 7 days`: this filter presents the attendance data for the last seven days." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:262 -msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields." +#: ../../content/applications/hr/attendances.rst:397 +msgid ":guilabel:`Add Custom Filter`: create a custom filter using the pop-up that appears when this is selected." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:270 -msgid ":guilabel:`Dependant`: If the employee has any children, enter the :guilabel:`Number of Children` in the field." +#: ../../content/applications/hr/attendances.rst:401 +msgid "Groups" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:272 -msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." +#: ../../content/applications/hr/attendances.rst:403 +msgid "The default groups that can be selected are:" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Add the private information to the Private Information tab." +#: ../../content/applications/hr/attendances.rst:405 +msgid ":guilabel:`Check In`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-in information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:284 -msgid "HR settings tab" +#: ../../content/applications/hr/attendances.rst:409 +msgid ":guilabel:`Employee`: this group presents the attendance data organized by employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:286 -msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." +#: ../../content/applications/hr/attendances.rst:410 +msgid ":guilabel:`Check Out`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-out information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:290 -msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :ref:`Related User `, with the drop-down menus." +#: ../../content/applications/hr/attendances.rst:414 +msgid ":guilabel:`Add Custom Group`: this option displays a drop-down menu with a variety of options to group the attendance data by, including :guilabel:`City`, :guilabel:`Country`, :guilabel:`Mode`, and :guilabel:`IP Address`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:292 -msgid ":guilabel:`Payroll`: Select the :guilabel:`Current Contract` and :guilabel:`Job Position` from the drop-down menus. If applicable, enter the :guilabel:`Registration Number` in this section." +#: ../../content/applications/hr/attendances.rst:421 +msgid "Errors" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:294 -msgid ":guilabel:`Previous Employer`: This section appears only for Belgian companies, and will not be visible for other locations. These are days that will be paid to the new employee. Enter any :guilabel:`Simple Holiday Pay to Recover`, :guilabel:`Number of Days to recover`, and :guilabel:`Recovered Simple Holiday Pay` from a previous employer, for both N and N-1 categories." +#: ../../content/applications/hr/attendances.rst:423 +msgid "Entries that contain an error appear on the dashboard in red. In the :guilabel:`Gantt view`, the entry appears with a red background. If in the :guilabel:`List view`, the entry text appears in red." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:298 -msgid ":guilabel:`Previous Occupations`: This section appears ony for Belgian companies, and will not be visible for other locations. Click :guilabel:`Add a line` to enter information for each previous occupation. Enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and the :guilabel:`Occupational Rate` in the corresponding fields. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." +#: ../../content/applications/hr/attendances.rst:426 +msgid "An error typically occurs when an employee has checked in but has not checked out within the last 24 hours, or when an employee has a check in and check out period spanning over 16 hours." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:303 -msgid ":guilabel:`Attendance/Point of Sale`: The employee's :guilabel:`Badge ID` and :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." +#: ../../content/applications/hr/attendances.rst:429 +msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:306 -msgid ":guilabel:`Application Settings`: If applicable, enter the :guilabel:`Fleet Mobility Card` number. Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The pop-up that allows for modifications to an attendance entry with an error. The calendar\n" +"selector is shown, and the time selector is highlighted." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Enter any information prompted in the HR Settings tab for the employee." +#: ../../content/applications/hr/attendances.rst:441 +msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:319 -msgid "Employees do not also need to be users. An employee does **not** count towards billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user must be created." +#: ../../content/applications/hr/attendances.rst:444 +msgid "To delete an entry, click :guilabel:`Remove` on the pop-up instead of making modifications to the entry." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:323 -msgid "In the :guilabel:`Related User` field, type in the name of the user to add, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Related User` form appears. Type in the :guilabel:`Name`, :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered. Once the record is saved, the new user appears in the :guilabel:`Related User` field." +#: ../../content/applications/hr/attendances.rst:448 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals.rst:754 +msgid "Reporting" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:330 -msgid "Documents" +#: ../../content/applications/hr/attendances.rst:450 +msgid "To view attendance reports, click :guilabel:`Reporting` in the top menu. The default report displays each employee's attendance information for the past 3 months, in a :guilabel:`Line Chart`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:332 -msgid "All documents associated with an employee are stored in the *Documents* app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button on the employee form. Click on the smart button, and all the documents appear. For more information on the *Documents* app, refer to the :doc:`Documents documentation `." +#: ../../content/applications/hr/attendances.rst:453 +msgid "The default view is a :guilabel:`Graph`. To view the data in a pivot table, click the :guilabel:`Pivot Table` button on the top right of the report. To switch back to the graph view, click the :guilabel:`Graph` button, located next to the :guilabel:`Pivot Table` button." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "All uploaded documents associated with the employee appear in the documents smart-button." +#: ../../content/applications/hr/attendances.rst:457 +msgid "To present different information, adjust the :ref:`filters and groups ` in the same way as in the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/payroll.rst:6 -#: ../../content/applications/hr/payroll/reporting.rst:39 -msgid "Payroll" +#: ../../content/applications/hr/attendances.rst:460 +msgid "The data can be presented in either a :guilabel:`Bar Chart`, :guilabel:`Line Chart`, :guilabel:`Pie Chart`, :guilabel:`Stacked` chart, or in :guilabel:`Descending` or :guilabel:`Ascending` order. To change the view to any of these charts, click the corresponding button above the displayed chart." msgstr "" -#: ../../content/applications/hr/payroll.rst:8 -msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." +#: ../../content/applications/hr/attendances.rst:464 +msgid "To change the :guilabel:`Measures`, click the :guilabel:`Measures` button and select the desired measure from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:12 -msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." +#: ../../content/applications/hr/attendances.rst:467 +msgid "The report can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a pop-up appears. Select the desired spreadsheet, and click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/hr/payroll.rst:18 -msgid "Settings" +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The default report view, with all the optional view buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll.rst:20 -msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here." +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" msgstr "" -#: ../../content/applications/hr/payroll.rst:23 -msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees." +#: ../../content/applications/hr/attendances/hardware.rst:6 +msgid "Kiosk management" msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Settings available for Payroll." +#: ../../content/applications/hr/attendances/hardware.rst:8 +msgid "A kiosk is a self-service station that allows employees to check in and check out for work shifts." msgstr "" -#: ../../content/applications/hr/payroll.rst:32 -msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "There are two ways to set up a kiosk:" msgstr "" -#: ../../content/applications/hr/payroll.rst:40 -#: ../../content/applications/hr/payroll/work_entries.rst:3 -msgid "Work entries" +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "**Laptop and desktop PC**" msgstr "" -#: ../../content/applications/hr/payroll.rst:42 -msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`." +#: ../../content/applications/hr/attendances/hardware.rst:14 +msgid "Running a kiosk in a web browser is the cheapest and most flexible option. You can print employee badges with any thermal or inkjet printer compatible with your web browser." msgstr "" -#: ../../content/applications/hr/payroll.rst:47 -msgid ":doc:`Manage work entries `" +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "**Tablet and mobile phone (Android or iOS)**" msgstr "" -#: ../../content/applications/hr/payroll.rst:50 -msgid "Work entry types" +#: ../../content/applications/hr/attendances/hardware.rst:19 +msgid "Tablets and mobile phones take up much less space, and their touchscreens are easy to use. Consider putting them in a secure stand at the front desk or mounting them securely on a wall." msgstr "" -#: ../../content/applications/hr/payroll.rst:52 -msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database." +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "We recommend using an iPad together with the `Heckler Design WindFall Stand `_" msgstr "" -#: ../../content/applications/hr/payroll.rst:57 -msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`." +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "RFID key fob readers" msgstr "" -#: ../../content/applications/hr/payroll.rst:60 -msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered." +#: ../../content/applications/hr/attendances/hardware.rst:29 +msgid "Employees can scan personal RFID key fobs with an RFID reader to manage check-ins and check-outs quickly and easily." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "List of all work entry types currently available." +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "An RFID key fob is placed on an RFID reader" msgstr "" -#: ../../content/applications/hr/payroll.rst:68 -msgid "New work entry type" +#: ../../content/applications/hr/attendances/hardware.rst:38 +msgid "We recommend using the `Neuftech USB RFID Reader `_." msgstr "" -#: ../../content/applications/hr/payroll.rst:70 -msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:" +#: ../../content/applications/hr/attendances/hardware.rst:41 +#: ../../content/applications/hr/attendances/hardware.rst:57 +msgid "An IoT box is **not** required." msgstr "" -#: ../../content/applications/hr/payroll.rst:73 -msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`." +#: ../../content/applications/hr/attendances/hardware.rst:44 +msgid "Barcode scanners" msgstr "" -#: ../../content/applications/hr/payroll.rst:75 -msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." +#: ../../content/applications/hr/attendances/hardware.rst:46 +msgid "Employees can scan the barcode on their employee badges to manage check-ins and check-outs quickly and easily. The kiosk mode works with most USB barcode scanners connected directly to a computer. Bluetooth barcode scanners are also supported natively." msgstr "" -#: ../../content/applications/hr/payroll.rst:78 -msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list." +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "We recommend using the `Honeywell product line `_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout." msgstr "" -#: ../../content/applications/hr/payroll.rst:80 -msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered." +#: ../../content/applications/hr/employees.rst:7 +msgid "Employees" msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "New work entry type form." +#: ../../content/applications/hr/employees.rst:9 +msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments." msgstr "" -#: ../../content/applications/hr/payroll.rst:89 -msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip." +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "Create a new employee" msgstr "" -#: ../../content/applications/hr/payroll.rst:92 -msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." +#: ../../content/applications/hr/employees/new_employee.rst:5 +msgid "When a new employee is hired, the first step is to create a new employee record. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`New` button and a new employee form appears. Fill out the required information and any additional details." msgstr "" -#: ../../content/applications/hr/payroll.rst:93 -msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." msgstr "" -#: ../../content/applications/hr/payroll.rst:94 -msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." +#: ../../content/applications/hr/employees/new_employee.rst:14 +msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields." msgstr "" -#: ../../content/applications/hr/payroll.rst:97 -msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours." +#: ../../content/applications/hr/employees/new_employee.rst:18 +msgid "General information" msgstr "" -#: ../../content/applications/hr/payroll.rst:103 -msgid "Working times" +#: ../../content/applications/hr/employees/new_employee.rst:20 +msgid "The employee form automatically saves as data is entered, but the save manually icon (a could with an up arrow inside it) may be clicked at any time to manually save the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:105 -msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list." +#: ../../content/applications/hr/employees/new_employee.rst:24 +#: ../../content/applications/hr/payroll/contracts.rst:39 +#: ../../content/applications/hr/payroll/payslips.rst:51 +msgid "Required fields" msgstr "" -#: ../../content/applications/hr/payroll.rst:109 -msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week." +#: ../../content/applications/hr/employees/new_employee.rst:26 +msgid ":guilabel:`Name`: Enter the employee's name." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "All working times currently set up in the database." +#: ../../content/applications/hr/employees/new_employee.rst:27 +msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." msgstr "" -#: ../../content/applications/hr/payroll.rst:119 -msgid "New working time" +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A new employee form with the required fields highlighted." msgstr "" -#: ../../content/applications/hr/payroll.rst:121 -msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form." +#: ../../content/applications/hr/employees/new_employee.rst:35 +#: ../../content/applications/hr/payroll/contracts.rst:66 +#: ../../content/applications/hr/payroll/payslips.rst:91 +#: ../../content/applications/hr/recruitment.rst:737 +msgid "Optional fields" msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "New working type form." +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid ":guilabel:`Photo`: In the top right image box of the employee form, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." msgstr "" -#: ../../content/applications/hr/payroll.rst:128 -msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time." +#: ../../content/applications/hr/employees/new_employee.rst:39 +msgid ":guilabel:`Job Position`: Enter the employee's job position title under their name, or select the job position from the :guilabel:`Job Position` drop-down menu to have this field auto-populate. The :guilabel:`Job Position` field under the employee name can be modified and does not need to match the selection made in the :guilabel:`Job Position` drop-down." msgstr "" -#: ../../content/applications/hr/payroll.rst:132 -msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time." +#: ../../content/applications/hr/employees/new_employee.rst:45 +msgid "It is recommended to have the job positions match, but if desired, the typed-in description in this field can contain more information than the selected drop-down job position." msgstr "" -#: ../../content/applications/hr/payroll.rst:138 -msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`." +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "An example where this may be applicable is if someone is hired for a sales representative position configured as :guilabel:`Sales Representative` in the *Recruitment* app, and that is selected for the drop-down :guilabel:`Job Position` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:141 -msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "In the typed in job position field beneath the employee's name, the position could be more specific, such as `Sales Representative - Subscriptions` if the employee is focused solely on subscription sales." msgstr "" -#: ../../content/applications/hr/payroll.rst:145 -msgid "Salary" +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." msgstr "" -#: ../../content/applications/hr/payroll.rst:150 -msgid "Structure types" +#: ../../content/applications/hr/employees/new_employee.rst:60 +msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee records. There is no limit to the amount of tags that can be added." msgstr "" -#: ../../content/applications/hr/payroll.rst:152 -msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)." +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "Work Contact Information: Enter the employee's :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." msgstr "" -#: ../../content/applications/hr/payroll.rst:158 -msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type." +#: ../../content/applications/hr/employees/new_employee.rst:65 +msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:164 -msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`." +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid ":guilabel:`Job Position`: Select the employee's job position from the drop-down menu. Once a selection is made, the :guilabel:`Job Position` field beneath the employee's name automatically updates to reflect the currently selected job position. These positions are from the :doc:`Recruitment <../../hr/recruitment/new_job/>` application, and reflect the currently \\ configured job positions." msgstr "" -#: ../../content/applications/hr/payroll.rst:167 -msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "List of all structure types." +#: ../../content/applications/hr/employees/new_employee.rst:72 +msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:175 -msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/employees/new_employee.rst:73 +msgid ":guilabel:`Next Appraisal Date`: This date automatically populates with a date that is computed according to the settings configured in the *Appraisals* application. This date can be modified using the calendar selector." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "New structure type box." +#: ../../content/applications/hr/employees/new_employee.rst:78 +msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:184 -msgid "Structures" +#: ../../content/applications/hr/employees/new_employee.rst:82 +msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`Internal Link` arrow next to the respective selection. The :guilabel:`Internal Link` arrow opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." msgstr "" -#: ../../content/applications/hr/payroll.rst:186 -msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules." +#: ../../content/applications/hr/employees/new_employee.rst:88 +msgid "Additional information tabs" msgstr "" -#: ../../content/applications/hr/payroll.rst:189 -msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`." +#: ../../content/applications/hr/employees/new_employee.rst:91 +msgid "Resumé tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:193 -msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`." +#: ../../content/applications/hr/employees/new_employee.rst:94 +msgid "Resumé" msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "All available salary structures." +#: ../../content/applications/hr/employees/new_employee.rst:96 +msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. When creating an entry for the first time, click :guilabel:`Create a new entry`, and the :guilabel:`Create Resumé lines` form appears. After an entry is added, the :guilabel:`Create a new entry` button is replaced with an :guilabel:`Add` button. Enter the following information for each entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:200 -msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." msgstr "" -#: ../../content/applications/hr/payroll.rst:203 -msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." +#: ../../content/applications/hr/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: Type in the title of the previous work experience." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Salary structure details for Regular Pay." +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Side Projects`, :guilabel:`Internal Certification`, :guilabel:`Completed Internal Training`, or type in a new entry, then click :guilabel:`Create \"(new entry)\"`." msgstr "" -#: ../../content/applications/hr/payroll.rst:211 -msgid "Rules" +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:213 -msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." msgstr "" -#: ../../content/applications/hr/payroll.rst:217 -msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." +#: ../../content/applications/hr/employees/new_employee.rst:116 +msgid ":guilabel:`Description`: Enter any relevant details in the field." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Rules for each salary structure type." +#: ../../content/applications/hr/employees/new_employee.rst:118 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." msgstr "" -#: ../../content/applications/hr/payroll.rst:224 -msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`." +#: ../../content/applications/hr/employees/new_employee.rst:123 +msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab, with the end date listed as *current*." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Enter the information for the new rule." +#: ../../content/applications/hr/employees/new_employee.rst:127 +msgid "Skills" msgstr "" -#: ../../content/applications/hr/payroll.rst:231 -msgid "The required fields for a rule are:" +#: ../../content/applications/hr/employees/new_employee.rst:129 +msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner that a resumé line is created. When creating a skill for the first time, click the :guilabel:`Create a new entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. After a skill is added, the :guilabel:`Create a new entry` button is replaced with an :guilabel:`Add` button. Enter the following information for each skill." msgstr "" -#: ../../content/applications/hr/payroll.rst:233 -msgid ":guilabel:`Name`: Enter a name for the rule." +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." msgstr "" -#: ../../content/applications/hr/payroll.rst:234 -msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." +#: ../../content/applications/hr/employees/new_employee.rst:139 +msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." msgstr "" -#: ../../content/applications/hr/payroll.rst:236 -msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them." +#: ../../content/applications/hr/employees/new_employee.rst:141 +msgid ":guilabel:`Skill`: After selecting a :guilabel:`Skill Type`, the corresponding skills associated with that selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new skill, then click :guilabel:`Create \"(new skill)\"`." msgstr "" -#: ../../content/applications/hr/payroll.rst:238 -msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." +#: ../../content/applications/hr/employees/new_employee.rst:146 +msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. First, select a :guilabel:`Skill Level`, then the progress bar automatically displays the pre-defined progress for that specific skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`Internal Link` arrow next to :guilabel:`Skill Level` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:240 -msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)." +#: ../../content/applications/hr/employees/new_employee.rst:152 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one skill to add, or click the :guilabel:`Save & New` button to save the current entry and immediately create a new entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:244 -msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next." +#: ../../content/applications/hr/employees/new_employee.rst:156 +msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." msgstr "" -#: ../../content/applications/hr/payroll.rst:250 -msgid "Rule parameters" +#: ../../content/applications/hr/employees/new_employee.rst:163 +msgid "Skill Types" msgstr "" -#: ../../content/applications/hr/payroll.rst:253 -msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +#: ../../content/applications/hr/employees/new_employee.rst:165 +msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Employee: Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`New` and a new :guilabel:`Skill Type` form appears. Fill out all the details for the new skill type. Repeat this for all the skill types needed." msgstr "" -#: ../../content/applications/hr/payroll.rst:258 -msgid "Other input types" +#: ../../content/applications/hr/employees/new_employee.rst:171 +msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This will act as the parent category for more specific skills and should be generic." msgstr "" -#: ../../content/applications/hr/payroll.rst:260 -msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`." +#: ../../content/applications/hr/employees/new_employee.rst:173 +msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the name for the new skill, then repeat for all other needed skills." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Other input types for payroll." +#: ../../content/applications/hr/employees/new_employee.rst:175 +msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a number for the :guilabel:`Progress` percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form. Once all the levels are entered, click the :guilabel:`Save manually` icon at the top of the screen. Next, select a default level for this skill type. Click :guilabel:`Set Default` on the line to be the default value. This is typically the lowest level, but any level can be set as the default. A check mark appears in the :guilabel:`Default Level` column, indicating which level is the default." msgstr "" -#: ../../content/applications/hr/payroll.rst:268 -msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/employees/new_employee.rst:185 +msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, click :guilabel:`Save & Close`, then click the :guilabel:`Save manually` icon at the top. Last, click :guilabel:`Set Default` on the `Beginner` line to set this as the default skill level." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Create a new Input Type." +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A skill form for a Math skill type, with all the information entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:278 -msgid "Salary package configurator" +#: ../../content/applications/hr/employees/new_employee.rst:197 +msgid "Work Information tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:280 -msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package." +#: ../../content/applications/hr/employees/new_employee.rst:199 +msgid "The Work Information tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Click on the :guilabel:`Work Information` tab to access this section, and enter the following information for the new employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:285 -msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information." +#: ../../content/applications/hr/employees/new_employee.rst:204 +msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` from the drop-down menu. To modify the address, hover over the first line (if there are multiple lines) of the address to reveal an :guilabel:`Internal Link` arrow. Click the :guilabel:`Internal Link` arrow to open up the company form, and make any edits. Use the breadcrumb menu to navigate back to the new employee form when done. If a new work address is needed, add the address by typing it in the field, then click :guilabel:`Create (new address)` to add the address, or :guilabel:`Create and edit...` to add the new address and edit the address form." msgstr "" -#: ../../content/applications/hr/payroll.rst:291 -msgid "Advantages" +#: ../../content/applications/hr/employees/new_employee.rst:211 +msgid ":guilabel:`Approvers`: In order to see this section, the user must have either :guilabel:`Administrator` or :guilabel:`Officer: Manage all employees` rights set for the :guilabel:`Employees` application. Using the drop-down menus, select the users responsible for approving :guilabel:`Expenses`, :guilabel:`Time Off`, and :guilabel:`Timesheets` for the employee. Hover over any of the selections to reveal the :guilabel:`Internal Link` arrow. Click the :guilabel:`Internal Link` arrow to open a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, :guilabel:`Mobile`, and :guilabel:`Default Warehouse` fields. These can be modified, if needed. Use the breadcrumb menu to navigate back to the new employee form when done." msgstr "" -#: ../../content/applications/hr/payroll.rst:293 -msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)." +#: ../../content/applications/hr/employees/new_employee.rst:220 +msgid ":guilabel:`Homeworking`: Using the drop-down menu, select the specific location the employee will work from, for each day of the week. The default options are :guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`. A new location can be typed into the field, then click either :guilabel:`Create (new location)` to add the location, or :guilabel:`Create and edit...` to add the new location and edit the form. After edits are done, click :guilabel:`Save & Close`, and the new location is added, and populates the field. For days the employee does not work, for example, Saturday and Sunday, leave the field blank (:guilabel:`Unspecified`)." msgstr "" -#: ../../content/applications/hr/payroll.rst:297 -msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`." +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "It is also possible to add or modify work locations by navigating to :menuselection:`Employees app --> Configuration --> Employee: Work Locations`. Click :guilabel:`New` to create a new location, then enter the details on the form. To modify a location, click on an existing location, then make any changes on the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Settings available for payroll." +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` for the employee. The :guilabel:`Internal Link` arrow opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here." msgstr "" -#: ../../content/applications/hr/payroll.rst:304 -msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/employees/new_employee.rst:239 +msgid "Working hours can also be modified in the *Payroll* application, where they are referred to as :guilabel:`Working Schedules`. For more information on how to create or modify :guilabel:`Working Schedules` in Payroll, refer to the :doc:`../../hr/payroll` documentation." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "List of advantages employee's can have." +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid ":guilabel:`Planning`: Click on a role from the drop-down menu for both the :guilabel:`Roles` and the :guilabel:`Default Role` fields to add a role. There is no limit to the amount of :guilabel:`Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Role`. The default role is the *typical* role that the employee performs, where the :guilabel:`Roles` are *all* the specific roles the employee is able to perform. The :guilabel:`Default Role` must be selected as a :guilabel:`Role`, if not, when the :guilabel:`Default Role` is selected, that role is automatically added to the list of :guilabel:`Roles`." msgstr "" -#: ../../content/applications/hr/payroll.rst:312 -msgid "The required fields for an advantage are:" +#: ../../content/applications/hr/employees/new_employee.rst:253 +msgid "The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. When planning work in the *Planning* app, employees can only be scheduled for specific work that corresponds to their selected roles. For example, only an employee with a *Functional Tester* role can be assigned to perform any activity that requires a *Functional Tester*." msgstr "" -#: ../../content/applications/hr/payroll.rst:314 -msgid ":guilabel:`Name`: Enter the name for the advantage." +#: ../../content/applications/hr/employees/new_employee.rst:260 +msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section must have *Administrator* rights set for the corresponding human resources role. To check who has these rights, go to :menuselection:`Settings app --> Users --> → Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." msgstr "" -#: ../../content/applications/hr/payroll.rst:315 -msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." +#: ../../content/applications/hr/employees/new_employee.rst:265 +msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they must have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." msgstr "" -#: ../../content/applications/hr/payroll.rst:317 -msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." +#: ../../content/applications/hr/employees/new_employee.rst:268 +msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they must have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." msgstr "" -#: ../../content/applications/hr/payroll.rst:320 -msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." +#: ../../content/applications/hr/employees/new_employee.rst:270 +msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they must have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." msgstr "" -#: ../../content/applications/hr/payroll.rst:324 -msgid "Personal info" +#: ../../content/applications/hr/employees/new_employee.rst:275 +msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." msgstr "" -#: ../../content/applications/hr/payroll.rst:326 -msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app." +#: ../../content/applications/hr/employees/new_employee.rst:278 +msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." msgstr "" -#: ../../content/applications/hr/payroll.rst:333 -msgid "An employee card can be thought of as an employee personnel file." +#: ../../content/applications/hr/employees/new_employee.rst:281 +msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." msgstr "" -#: ../../content/applications/hr/payroll.rst:335 -msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`." +#: ../../content/applications/hr/employees/new_employee.rst:286 +msgid "After the new working time is created, or an existing one is modified, select the employee's working hours using the drop-down menu in the :guilabel:`Schedule` section of the :guilabel:`Work Information` tab." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Personal information that appear on employee cards to enter." +#: ../../content/applications/hr/employees/new_employee.rst:291 +msgid "Private Information tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:343 -msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits." +#: ../../content/applications/hr/employees/new_employee.rst:293 +msgid "No information in the :guilabel:`Private Information` tab is required to create an employee, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "New personal information entry." +#: ../../content/applications/hr/employees/new_employee.rst:298 +msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Education`, :guilabel:`Work Permit`, :guilabel:`Family Status`, :guilabel:`Emergency` contact, and :guilabel:`Citizenship` information is entered. Fields are entered either using a drop-down menu, activating a check box, or typing in the information." msgstr "" -#: ../../content/applications/hr/payroll.rst:351 -msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card." +#: ../../content/applications/hr/employees/new_employee.rst:303 +msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`Internal Link` arrow to open the address form. On the address form, enter or edit the necessary details. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:355 -msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "Enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the respective fields. Next, enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. If the bank is not already configured (the typical situation when creating a new employee) enter the bank account number, and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account Number` form loads. Fill in the information, then click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/payroll.rst:359 -msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry." +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "Then, select the employee's preferred :guilabel:`Language` from the drop-down menu. Next, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits. Lastly, enter the employee's license plate information in the :guilabel:`Private Car Plate` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:362 -msgid "Resume" +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." msgstr "" -#: ../../content/applications/hr/payroll.rst:365 -msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +#: ../../content/applications/hr/employees/new_employee.rst:324 +msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` (visa number) and/or :guilabel:`Work Permit No` (work permit number) in the corresponding fields. Using the calendar selector, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:3 -msgid "Contracts" +#: ../../content/applications/hr/employees/new_employee.rst:330 +msgid ":guilabel:`Family Status`: Select the current :guilabel:`Marital Status` using the drop-down menu, either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced`. If the employee has any dependent children, enter the :guilabel:`Number of Dependent Children` in the field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:5 -msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, their working hours, and any other details about their position." +#: ../../content/applications/hr/employees/new_employee.rst:334 +msgid ":guilabel:`Emergency`: Type in the :guilabel:`Contact Name` and :guilabel:`Contact Phone` number of the employee's emergency contact in the respective fields." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:10 -msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed in order to send and sign contracts. Please refer to the :doc:`/applications/finance/documents` and :doc:`/applications/finance/sign` documentation." +#: ../../content/applications/hr/employees/new_employee.rst:336 +msgid ":guilabel:`Citizenship`: This section contains all the information relevant to the citizenship of the employee. Some fields use a drop-down menu, as the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` fields do. The :guilabel:`Date of Birth` uses a calendar selector to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No` (identification number, :guilabel:`Passport No` (passport number), and :guilabel:`Place of Birth` fields. Last, if the employee is not a resident of the country they are working in, activate the check box next to the :guilabel:`Non-resident` field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:15 -msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Employees --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a default kanban view. The default view displays both running contracts and contracts that need action. Expired and canceled contracts are hidden in the default view." +#: ../../content/applications/hr/employees/new_employee.rst:350 +msgid "HR Settings tab" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Contracts dashboard view showing running contracts and contracts with issues." +#: ../../content/applications/hr/employees/new_employee.rst:352 +msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:25 -msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application. The default contracts view in the *Payroll* application displays running contracts and contracts needing attention, while the default contracts view in the *Employees* application displays all contracts in a kanban view, organized by their stage, regardless of status. All contracts can be viewed by changing the filters." +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :guilabel:`Related User`, with the drop-down menus. The :guilabel:`Employee Type` options include :guilabel:`Employee`, :guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, or :guilabel:`Freelancer`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:32 -msgid "Create a new contract" +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "Employees do not also need to be users. *Employees* do **not** count towards the Odoo subscription billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user must be created. After the :guilabel:`User` is created and saved, the new user will appear in the :guilabel:`Related User` field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:34 -msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the contracts dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold." +#: ../../content/applications/hr/employees/new_employee.rst:367 +msgid "After the employee is created, create the user. Click the :guilabel:`⚙️ (gear)` icon, then click :guilabel:`Create User`. A :guilabel:`Create User` form appears. Type in the :guilabel:`Name` and :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered, and the employee record is automatically updated with the newly created user populating the :guilabel:`Related User` field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "New contract form to be filled in when creating a new contract." +#: ../../content/applications/hr/employees/new_employee.rst:373 +msgid "Users can also be created manually. For more information on how to manually add a user, refer to the :doc:`../../general/users/manage_users` document." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:45 -msgid ":guilabel:`Contact Reference`: Type in the name or title for the contract, such as `John Smith Contract`." +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid ":guilabel:`Payroll`: If applicable, enter the :guilabel:`Registration Number of the Employee` in this section. The :guilabel:`Attestation (N-1)` and :guilabel:`Attestation (N)` sections appear only for Belgian companies, and will not be visible for other locations. These sections log the days that will be paid to the new employee. Enter any :guilabel:`Amount to recover`, :guilabel:`Number of days`, and :guilabel:`Recovered Amount` of :guilabel:`Holiday Attest (year) - Simple Holiday Pay from previous employer to recover in (year)`, for both N and N-1 categories. For the :guilabel:`Holiday Attest (year) - Previous occupation for Double Holiday Pay Recovery in (year)` section, click :guilabel:`Add a line`, and enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and :guilabel:`Occupation Rate`. Repeat for all entries. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:47 -msgid ":guilabel:`Company`: Select the company the contract applies to by clicking on the drop-down menu. A new company can be created by typing the name in the field, then clicking either :guilabel:`Create` to create the new company, or :guilabel:`Create and Edit` to create the new company and edit the company details." +#: ../../content/applications/hr/employees/new_employee.rst:386 +msgid ":guilabel:`SD WORX`: Enter the employee's seven digit :guilabel:`SDWorx code` in this field, if applicable." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:51 -msgid ":guilabel:`Salary Structure Type`: Select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field." +#: ../../content/applications/hr/employees/new_employee.rst:388 +msgid ":guilabel:`Attendance/Point of Sale/Manufacturing`: The employee's :guilabel:`PIN Code` and :guilabel:`Badge ID` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID. The :guilabel:`PIN Code` is used to sign in and out of the *Attendance* app kiosk, and a :abbr:`POS (Point Of Sale)` system." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:54 -msgid ":guilabel:`Start Date`: The date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :guilabel:`< > (arrow)` icons, then clicking on the :guilabel:`date`." +#: ../../content/applications/hr/employees/new_employee.rst:393 +msgid ":guilabel:`Application Settings`: Enter the employee's :guilabel:`Hourly Cost` in a XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount. This value does not affect the *Payroll* application. If applicable, enter the :guilabel:`Fleet Mobility Card` number." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:57 -msgid ":guilabel:`Working Schedule`: Select one of the working schedules from the drop-down menu." +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Enter any information prompted in the HR Settings tab for the employee." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:60 -msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll --> Configuration --> Working Times` and either :guilabel:`Create` a new working time or click on an existing working time and edit it by clicking :guilabel:`Edit`." +#: ../../content/applications/hr/employees/new_employee.rst:405 +msgid "Documents" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:68 -msgid ":guilabel:`Employee`: Name of the employee that the contract applies to." +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "All documents associated with an employee are stored in the :guilabel:`Documents` app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button above the employee record. Click on the smart button, and all the documents appear. For more information on the :guilabel:`Documents` app, refer to the :doc:`../../finance/documents` documentation." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:69 -msgid ":guilabel:`Department`: The department the contract applies to." +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "All uploaded documents associated with the employee appear in the documents smart-button." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:70 -msgid ":guilabel:`Job Position`: The specific job position the contract applies to." +#: ../../content/applications/hr/fleet.rst:7 +msgid "Fleet" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:71 -msgid ":guilabel:`Contract Type`: Choose from :guilabel:`CDI`, :guilabel:`CDD`, or :guilabel:`PFI` from the drop-down menu." +#: ../../content/applications/hr/fleet.rst:9 +msgid "Odoo *Fleet* organizes all the vehicles, contracts, and repairs of all the vehicles." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:74 -msgid ":guilabel:`CDI` is an open-ended contract with only a start date but no end date." +#: ../../content/applications/hr/fleet/configuration.rst:3 +msgid "Configuration menu" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:75 -msgid ":guilabel:`CDD` is a contract with both a start date and an end date." +#: ../../content/applications/hr/fleet/configuration.rst:5 +msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, :ref:`vehicle models `, and :ref:`model categories `." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:76 -msgid ":guilabel:`PFI` is a Belgian-specific contract used when hiring employees that need training, and covers the training period specifically." +#: ../../content/applications/hr/fleet/configuration.rst:13 +#: ../../content/applications/hr/payroll.rst:18 +msgid "Settings" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:79 -msgid ":guilabel:`End Date`: If the contract has a specific end date, click the drop-down menu, navigate to the correct month and year using the arrow icons, then click on the date." +#: ../../content/applications/hr/fleet/configuration.rst:15 +msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are two settings that need configuration, the vehicle contract end date alert delay, and a new vehicle request limit." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:81 -msgid ":guilabel:`HR Responsible`: If there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu." +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Settings available for the Fleet application." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:83 -msgid ":guilabel:`Analytic Account`: This field allows a link between the contract and a specific analytic account for accounting purposes." +#: ../../content/applications/hr/fleet/configuration.rst:24 +msgid "End Date Contract Alert" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:87 -msgid "Contract details" +#: ../../content/applications/hr/fleet/configuration.rst:26 +msgid "The :guilabel:`End Date Contract Alert` field defines an alert delay for the persons responsible for vehicle contracts. The responsible person(s) will receive an email informing them a vehicle contract is about to expire in the number of days defined in this field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:89 -msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." +#: ../../content/applications/hr/fleet/configuration.rst:31 +msgid "To determine who the responsible person is for a contract, open an individual contract. The person listed as :guilabel:`Responsible` under the :guilabel:`Contract Information` section of the contract is the person who will receive the alert." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Contract details in optional tabs for a new contract." +#: ../../content/applications/hr/fleet/configuration.rst:35 +msgid "To access all contracts, navigate to :menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear in the list. Click on a :guilabel:`Contract` to view it." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:96 -msgid ":guilabel:`Contract Template`: Select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application." +#: ../../content/applications/hr/fleet/configuration.rst:38 +msgid "An individual contract can also be found by navigating to :menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual vehicle. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contract(s) associated with this vehicle only appears in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:98 -msgid ":guilabel:`New Contract Document Template`: Select a contract from the drop-down menu to be modified for this new employee contract." +#: ../../content/applications/hr/fleet/configuration.rst:45 +msgid "New Vehicle Request" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:100 -msgid ":guilabel:`Contract Update Document Template`: Select a contract from the drop-down menu if the employee has an existing contract that requires updating." +#: ../../content/applications/hr/fleet/configuration.rst:47 +msgid "The :guilabel:`New Vehicle Request` field sets a limit on how many new vehicles are requested based on fleet availability. An employee filling out the salary configurator form (after being offered a position), will *not* be able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:102 -msgid ":guilabel:`Notes`: The notes field is a text field where any notes for the employee contract can be entered for future reference." +#: ../../content/applications/hr/fleet/configuration.rst:54 +msgid "If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and there are 25 vehicles available, an employee would not be able to request a new vehicle. If there are only 10 cars available, then the employee would be able to request a new vehicle." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:106 -msgid "Modifying a contract" +#: ../../content/applications/hr/fleet/configuration.rst:61 +msgid "Manufacturers" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:108 -msgid "Click the :guilabel:`External Link` button at the end of each line to open the corresponding contract template and make any changes." +#: ../../content/applications/hr/fleet/configuration.rst:63 +msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car and bicycle manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Manufacturers`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:115 -msgid "A pop-up window appears with all the contract details. Modify the fields for the contract as needed." +#: ../../content/applications/hr/fleet/configuration.rst:67 +msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty six pre-configured :ref:`models ` from four major auto manufacturers and one major bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Edit the details for the contract." +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Manufacturer card with the amount of models listed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:121 -msgid ":guilabel:`Tags`: Select any tags associated with the contract." +#: ../../content/applications/hr/fleet/configuration.rst:77 +msgid "Add a manufacturer" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:122 -msgid ":guilabel:`Signed Document Workspace`: This is where the signatures are stored. Choose a pre-configured workspace or create a new one." +#: ../../content/applications/hr/fleet/configuration.rst:79 +msgid "To add a new manufacturer to the database, click :guilabel:`Create`. A manufacturer form will load. Only two pieces of information are needed, the :guilabel:`Name` of the manufacturer, and the logo. Type the name of the manufacturer in the name field, and select an image to upload for the logo. When the information is entered, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:124 -msgid ":guilabel:`Signed Document Tags`: Select or create any tags associated only with the signed contract as opposed to the original unsigned contract." +#: ../../content/applications/hr/fleet/configuration.rst:87 +msgid "Vehicle Models" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:126 -msgid ":guilabel:`Redirect Link`: Enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another, in this case, to the newly updated contract specifically written for them." +#: ../../content/applications/hr/fleet/configuration.rst:89 +msgid "Many manufacturers have a variety of models that they produce. When adding a vehicle to the fleet, it is important to specify the vehicle model being added. Odoo comes with pre-configured car models from four major auto manufacturers, and one pre-configured bicycle model from one bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle). If a vehicle *other* than the pre-configured models from these manufacturers are part of a fleet, the model (and/or manufacturer) will need to be added to the database." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:129 -msgid ":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or :guilabel:`On Invitation`." +#: ../../content/applications/hr/fleet/configuration.rst:97 +msgid "Preconfigured Models" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:131 -msgid ":guilabel:`All Users`: Any user in the organization can sign the contract." +#: ../../content/applications/hr/fleet/configuration.rst:99 +msgid "The following models are pre-loaded in Odoo and do not need to be added to the database:" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:132 -msgid ":guilabel:`On Invitation`: Only users selected in this field can sign the contract." +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "AUDI" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:134 -msgid ":guilabel:`Invited Users`: Select the person(s) that can sign the document." +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "BMW" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:135 -msgid ":guilabel:`Document`: The attached document can be replaced by clicking the :guilabel:`✏️ (pencil)` icon. A pop-up window appears so another document can be selected for upload. The file must be a PDF. To remove the document, click the :guilabel:`🗑️ (trash can)` icon." +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Eddy Merckx" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:139 -msgid "Once the edits are complete, click the :guilabel:`Save` button. All the information for the selected contract template populates the fields in the :guilabel:`Salary Information` tab. Any additional tabs, such as :guilabel:`Personal Documents`, appears if applicable." +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Mercedes" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:144 -msgid "Salary information" +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Opel" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Optional tabs for a new contract." +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "A1" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:150 -msgid "This section is where the specific salary details are defined. This section is country-specific, so depending on where the company is located, these fields may vary." +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Serie 1" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:153 -msgid "Enter the amount in the various fields, or check a box to apply a benefit. Some options that can be entered here include :guilabel:`Meal Vouchers`, :guilabel:`Fuel Card`, :guilabel:`Internet`, :guilabel:`Paid Time Off`, etc." +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "SanRemo76" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:157 -msgid "Some fields may be automatically filled in based off of the contracts selected in the :guilabel:`Contract Details` tab." +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Class A" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:161 -msgid "Attachment of salary" +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Agilia" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:163 -msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. This section is where all of these deductions or allocations are set." +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "A3" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:167 -msgid "To add a new deduction, click :guilabel:`Add a line`. Type in a description for the allocation under :guilabel:`Description`." +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Serie 3" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Enter a new line for each type of garnishment." +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Class B" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:174 -msgid "Select the :guilabel:`Garnished Type` from the drop-down menu. Choose from:" +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Ampera" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:176 -msgid ":guilabel:`Attachment of Salary`: Any payments taken out towards something that is *not* child support. Typically any garnishments such as lawsuit payments, payments toward taxes owed, etc." +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "A4" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:178 -msgid ":guilabel:`Assignment of Salary`: Any deduction that is not required but voluntary, such as a pre-tax allocation to a college savings account." +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Serie 5" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:180 -msgid ":guilabel:`Child Support`: Any payments taken out specifically for child support." +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Class C" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:182 -msgid "Enter the start and end dates the entry applies to. Click on the drop-down menu under :guilabel:`From` and :guilabel:`To`, navigate to the correct month and year by using the :guilabel:`< > (arrow)` icons, then click on the :guilabel:`date`." +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Antara" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:186 -msgid "Last, enter the :guilabel:`Amount` that each payslip pays towards the entry." +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "A5" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:188 -msgid "To delete a line, click the :guilabel:`🗑️ (trash can)` icon at the end of the line." +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Serie 6" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:191 -msgid "Save and send the contract" +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Class CL" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:193 -msgid "Once a contract has been created and/or modified, save the contract by clicking the :guilabel:`Save` button. Next, the contract must be sent to the employee to be signed." +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Astra" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:196 -msgid "Click on one of the following buttons to send the contract to the employee:" +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "A6" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Send the contract to the employee via one of the buttons." +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Serie 7" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:202 -msgid ":guilabel:`Generate Simulation Link`: This option is for Belgian companies only. Clicking this opens a pop-up window that contains the basic information from the contract as well as a link for the contract when using the salary configurator. Click :guilabel:`Send Offer` to send an email to the employee so they can sign the contract." +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Class CLS" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:0 -msgid "Sends a link to the employee for the contract." +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "AstraGTC" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:212 -msgid "In order to send a contract using the :guilabel:`Generate Simulation Link`, there must be a signature field in the contract PDF being sent to the employee so they can sign it." +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "A7" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:215 -msgid ":guilabel:`Signature Request`: Click this and a pop-up window appears where an email can be typed to the employee. Select the document, such as a contract, NDA, or Homeworking Policy, from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent." +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Serie Hybrid" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:0 -msgid "Request a signature for the contract via email." +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Class E" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:224 -msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off." +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Combo Tour" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:3 -msgid "Payslips" +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "A8" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:5 -msgid "Payslips are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured." +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Serie M" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:10 -msgid "The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` application consists of three sections: :guilabel:`To Pay`, :guilabel:`All Payslips`, and :guilabel:`Batches`." +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Class GL" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:13 -msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips." +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Corsa" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Payslips menu selection in Payroll." +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Q3" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:21 -msgid "To pay" +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Serie X" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:23 -msgid "Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the payslips that need to be paid. On this page, Odoo displays the payslips that have not been generated yet, and can be created from this dashboard." +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Class GLK" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "View all payslips that need to be paid on the Payslips To Pay page." +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Insignia" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:31 -msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Q5" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:36 -msgid "Clicking on an individual payslip entry will show the details for the individual payslip." +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Serie Z4" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:41 -msgid "Create new payslip" +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Class M" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:43 -msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner." +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Meriva" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:47 -msgid "Clicking :guilabel:`Create` reveals a blank payslip form, wherein the necessary payslip information can be entered." +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Q7" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:53 -msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines." +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Class R" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "The necessary fields for a new payslip." +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Mokka" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:60 -msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app." +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "TT" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:66 -msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below." +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Class S" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:70 -msgid ":guilabel:`Contract`: Using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options." +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Zafira" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:72 -msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options." +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Class SLK" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:75 -msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`." +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Zafira Tourer" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:77 -msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu." +#: ../../content/applications/hr/fleet/configuration.rst:128 +msgid "Class SLS" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:79 -msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application." +#: ../../content/applications/hr/fleet/configuration.rst:134 +msgid "Add a new model" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "The necessary fields for a new payslip in the Accounting Information tab." +#: ../../content/applications/hr/fleet/configuration.rst:136 +msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Vehicle Models`. Click :guilabel:`Create` and a vehicle model form will load. Enter the following information on the form, then click :guilabel:`Save`. Be advised, some fields are specific to Belgian based companies, so not all fields or sections may be visible depending on the location of the company." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:87 -msgid "It is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." +#: ../../content/applications/hr/fleet/configuration.rst:142 +msgid ":guilabel:`Model name`: enter the model name in the field." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:93 -msgid ":guilabel:`Reference`: Any note or reference message for the new entry can be entered here." +#: ../../content/applications/hr/fleet/configuration.rst:143 +msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer and then click :guilabel:`Create` or :guilabel:`Create & Edit`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:94 -msgid ":guilabel:`Company Car`: If applicable, select the company car from the drop-down." +#: ../../content/applications/hr/fleet/configuration.rst:146 +msgid ":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it will affect payroll." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:95 -msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." +#: ../../content/applications/hr/fleet/configuration.rst:150 +msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category and then click :guilabel:`Create (new category)`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:155 +msgid "When the manufacturer is selected, the logo for the manufacturer will automatically load in the image box in the top right corner." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:159 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:162 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:164 +msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:165 +msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:166 +msgid ":guilabel:`Color`: enter the color of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:167 +msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:168 +msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:171 +#: ../../content/applications/hr/payroll.rst:211 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:174 +msgid "The :guilabel:`Salary` section only appears for Belgian-based companies, and only if the company has their localization setting set to Belgium. The cost values are all **monthly** with the exception of the :guilabel:`Catalog Value (VAT Incl.)`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:178 +msgid ":guilabel:`Can be requested`: check this box if employees can request this model vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:179 +msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the :abbr:`MSRP (Manufacturer's Suggested Retail Price)` for the vehicle at the time of purchase or lease." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:181 +msgid ":guilabel:`C02 fee`: this value is automatically calculated based on Belgian laws and regulations, and cannot be modified. The value is based on the value entered in the :guilabel:`CO2 Emissions` field in the :guilabel:`Engine` section of the vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:186 +msgid "Modifying the :guilabel:`CO2 Emissions` field will adjust the value in the :guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:189 +msgid ":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, which appears in the salary configurator that is available to a future employee when they are offered a job position. This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws. The :guilabel:`Cost (Depreciated)` does not depreciate automatically on the *vehicle model*, it only depreciates based on the *contract* linked to a specific vehicle and not on the general model." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:195 +msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and also is depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:199 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:201 +msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses form the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:205 +msgid ":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the vehicle produces in grams per kilometer (g/km). This information is provided by the car manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:207 +msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:209 +msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:211 +msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:213 +msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:214 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:217 +msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:221 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:223 +msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors used by the *Purchase* app." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:227 +msgid "The vendor(s) the vehicle can be purchased from may be added in this tab. To add a vendor, click :guilabel:`Add`, and a pop-up loads with a list of all the vendors currently in the database. Select the vendor to add by clicking the checkbox next to the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:232 +msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`Create`. A vendor form will load. Enter the information in the vendor tab, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:244 +msgid "Model Category" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:246 +msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet. Model categories are set on the :ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:250 +msgid "To view all the models currently set up, navigate to :menuselection:`Fleet application --> Configuration --> Model Category`. All models are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:254 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:256 +msgid "To add a new category, click :guilabel:`Create`. A new entry line appears at the bottom of the list. Type in the new category, then click :guilabel:`Save` to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:259 +msgid "To reorganize how the categories appear in the list, click on the up and down arrows to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "List view of the models in the fleet." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Create new vehicles" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:5 +msgid "Odoo's *Fleet* app manages all vehicles and the accompanying documentation that comes with vehicle maintenance and driver's records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "All vehicles are organized on the main :guilabel:`Fleet` dashboard. Each vehicle has its own *vehicle form*, which is displayed as a card in the kanban view, according to it's status. Every vehicle form is displayed in its current corresponding kanban stage. The default stages are :guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Ordered`, :guilabel:`Registered`, :guilabel:`Downgraded`, :guilabel:`Reserve`, and :guilabel:`Waiting List`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:14 +msgid "To add a new vehicle to the fleet, click the :guilabel:`Create` button, and a blank vehicle form loads. Enter the vehicle information in the vehicle form, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:20 +msgid ":guilabel:`Model`: select the vehicle's model from the drop-down menu. If the model is not listed, type in the model name and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:22 +msgid ":guilabel:`License Plate`: enter the vehicle's license plate number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid ":guilabel:`Tags`: select any tags from the drop-down menu, or type in a new tag. There is no limit on the amount of tags that can be selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "The :guilabel:`Model` is the only required field on the new vehicle form. When a model is selected, other fields will appear on the vehicle form, and relevant information will auto-populate fields that apply to the model. If some of the fields do not appear, this may indicate there is no model selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:33 +msgid "Driver section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:35 +msgid "This section of the vehicle form relates to the person who is currently driving the car, as well as any plans for a change in the driver in the future, and when." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:38 +msgid ":guilabel:`Driver`: select the driver from the drop-down menu, or type in a new driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:40 +msgid ":guilabel:`Mobility Card`: if the selected driver has a mobility card listed on their employee card in the *Employees* application, the mobility card number will appear in this field. If there is no mobility card listed and one should be added, :ref:`edit the employee card ` in the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:44 +msgid ":guilabel:`Future Driver`: if the next driver for the vehicle is known, select the next driver from the drop-down menu, or type in the next driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid ":guilabel:`Plan To Change Car`: if the current driver set for this vehicle plans to change their vehicle, either because they are waiting on a new vehicle that is being ordered, or this is a temporary vehicle assignment and they know which vehicle they will be driving next, check this box. If the current driver does not plan to change their vehicle and use this current vehicle, do not check this box." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:52 +msgid ":guilabel:`Assignment Date`: select the date the vehicle will be available for another driver using the drop-down calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. If this field is blank, this indicates the vehicle is currently available and can be reassigned to another driver. If it is populated, the vehicle will not be available to assign to another driver until the date entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:60 +msgid "A driver does **not** have to be an employee, but a driver must be listed in the *Contacts* application. When creating a new driver, the driver is added to the *Contacts* application, not the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "Vehicle section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "This section of the vehicle form relates to the physical vehicle, it's various properties, when it was added, where it is located, and who is managing it." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:70 +msgid ":guilabel:`Immatriculation Date`: select the date the vehicle is acquired using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:72 +msgid ":guilabel:`Cancellation Date`: select the date the vehicle lease will expire, or when the vehicle will be no longer available, using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:74 +msgid ":guilabel:`Chassis Number`: enter the chassis number in the field. This is known in some countries as the :abbr:`VIN (Vehicle Identification Number)` number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:76 +msgid ":guilabel:`Last Odometer`: enter the last known odometer reading in the number field. Using the drop-down menu next to the number field, select whether the odometer reading is in kilometers :guilabel:`(km)` or miles :guilabel:`(mi)`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:79 +msgid ":guilabel:`Fleet Manager`: select the fleet manager from the drop-down menu, or type in a new fleet manager and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:81 +msgid ":guilabel:`Location`: type in the location for the vehicle in the field. The most common scenario for when this field would be populated is if a company has several office locations. The typical office location where the vehicle is located would be the location entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid ":guilabel:`Company`: select the company that the vehicle will be used for and associated with from the drop-down menu, or type in a new company and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:89 +msgid "Creating a new company may cause a subscription price change depending on the current plan. Refer to `Odoo's pricing plan `_ for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "The new vehicle form, showing the vehicle tax section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:100 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:102 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicles engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid ":guilabel:`Disallowed Expense Rate`: this is the amount of non-deductible expenses for the vehicle. This amount is not counted towards any deductions on a tax return or as an allowable expense when calculating taxable income. It is recommended to check with the accounting department to ensure the value(s) entered are correct." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:110 +msgid ":guilabel:`Start Date`: enter the :guilabel:`Start Date` and :guilabel:`(%) Percentage` for when the :guilabel:`Disallowed Expense Rate` value goes into effect. Click :guilabel:`Add a line` to enter a date. Click on the blank line to display a calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. Enter the percentage that is disallowed in the :guilabel:`% (percent)` field to the right of the date. The percentage should be entered in an XX.XX format. Repeat this for all entries needed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:119 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:121 +msgid ":guilabel:`First Contract Date`: select the start date for the vehicle's first contract using the drop-down calendar. Typically this is the day the vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the MSRP (Manufacturer's Suggested Retail Price) for the vehicle at the time of purchase or lease." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:125 +msgid ":guilabel:`Purchase Value`: enter the purchase price or the value of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid ":guilabel:`Residual Value`: enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:129 +msgid "The values listed above will affect the accounting department. It is recommended to check with the accounting department for more information and/or assistance with these values." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:137 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:139 +msgid "If the model for the new vehicle is already configured in the database, the :guilabel:`Model` tab will be populated with the corresponding information. If the model is not already in the database and the :guilabel:`Model` tab needs to be configured, :ref:`configure the new vehicle model `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "Check the information in the :guilabel:`Model` tab to ensure it is accurate. For example, the color of the vehicle, or whether there is a trailer hitch installed or not, are examples of information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:153 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:155 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:3 +msgid "Services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:5 +msgid "To properly maintain a fleet of vehicles, regular maintenance as well as periodic repairs are needed. Scheduling repairs and managing services for an entire fleet is necessary to ensure all vehicles are in good working order when they are needed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:10 +msgid "Create a service record" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:12 +msgid "To log a service, go to the main services dashboard by navigating to :menuselection:`Fleet app --> Fleet --> Services`. Click :guilabel:`Create` and a service form appears. Fill in the information on the form and click :guilabel:`Save`. The only two fields that are required to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "The fields are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:19 +msgid ":guilabel:`Description`: enter in a short description of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:20 +msgid ":guilabel:`Service Type`: select the type of service performed from the drop-down menu, or type in a new type of service and click either :guilabel:`Create` or :guilabel:`Create & Edit...`. This list is not pre-configured in Odoo. When creating a fleet and logging a service, the types of service need to be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid ":guilabel:`Date`: using the calendar module, select the date the service was provided or is scheduled to be performed. Navigate to the desired month using the left and right arrow icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid ":guilabel:`Cost`: enter the cost of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:28 +msgid ":guilabel:`Vendor`: select the vendor who performed the service from the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name and click either :guilabel:`Create` to add them, or :guilabel:`Create & Edit...` to create the vendor and edit the vendor form. The vendor form allows for other details aside form the name to be entered, such as contact information." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid ":guilabel:`Vehicle`: select the vehicle that was serviced from the drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field is populated, and the unit of measure for the :guilabel:`Mileage` field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:36 +msgid ":guilabel:`Driver`: the current driver listed for the selected vehicle is populated when the :guilabel:`Vehicle` is selected. If the driver needs to be changed, another driver can be selected from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:39 +msgid ":guilabel:`Odometer Value`: enter the odometer reading when the service was done. The units of measure will either be in kilometers (:guilabel:`km`) or miles (:guilabel:`mi`). When the :guilabel:`Vehicle` is selected, the units of measure is populated. This comes from the vehicle form. To change from kilometers to miles, or vice versa, click the :guilabel:`External Link` button next to the vehicle selected in the :guilabel:`Vehicle` field. Change the unit of measure, then click :guilabel:`Save`. the unit of measure will be updated in the :guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:46 +msgid ":guilabel:`Notes`: enter any notes for the repair in the notes tab at the bottom of the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Enter the information for a new service. The required fields are Service Type and Vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:54 +msgid "List of services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:56 +msgid "To view all services logged in the database, including old and new requests, go to :menuselection:`Fleet application --> Fleet --> Services`. All services appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:60 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid ":guilabel:`Date`: the date service or repair was performed or is requested to be performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:63 +msgid ":guilabel:`Description`: a short description of the specific type of service or repair performed to clarify the specific service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:65 +msgid ":guilabel:`Service Type`: the service or repair performed. This is selected from a list of services that must be configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:67 +msgid ":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:68 +msgid ":guilabel:`Driver`: who the current driver is for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:69 +msgid ":guilabel:`Vendor`: the specific vendor who performed the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:70 +msgid ":guilabel:`Cost`: the total cost for the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:71 +msgid ":guilabel:`Notes`: any information associated with the service or repair that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid ":guilabel:`Stage`: the status of the service or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Canceled`, or :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:81 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:83 +msgid "It is recommended to view the list of services in one of several pre-configured ways to better view the information presented. In the top right corner of the list, there are several icons that when clicked, sort the data in different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The icons in the top right corner than cn be clicked to present the information in\n" +"different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:93 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "The default view of the services is the list view. This presents all the services in chronological order, from oldest to newest, in a list." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:98 +msgid "The information can be sorted by any column. At the top of each column, hover over the column name. An arrow appears to the right of the name. Click the arrow to sort the data by that specific column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "The default sorting is descending alphabetical order (A to Z). Click the arrow again to reverse the order, and go in reverse alphabetical order (Z to A). The one exception to this sorting is the default :guilabel:`Date` column, which sorts the information in chronological order (January to December) instead of alphabetical order." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:107 +#: ../../content/applications/hr/recruitment.rst:33 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "To view services by their stage, click on the :guilabel:`Kanban icon`, which is the second icon in the top right, and appears as four black squares in a cube." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:112 +msgid "All the services with the same status appear in the corresponding column, from :guilabel:`Running` to :guilabel:`Cancelled`. To change the status of a service, simply click and drag the service card to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:117 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:119 +msgid "Another way to view the data is in a graph. To view the graph, click the :guilabel:`Graph icon`, which is the third icon in the top right, and appears as a small graph." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +msgid "The graph displays the information in a graph where the X axis represents the :guilabel:`Date` and the Y axis represents the :guilabel:`Cost`. Each column represents a single month, and then is further organized by vehicle. Each vehicle is represented by a different color, and each month's bar is divided by each vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:130 +msgid "The final way to view the service data is in a spreadsheet pivot table. Click on the :guilabel:`Pivot icon`, which is the last icon in the top right, and appears as a small spreadsheet." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:133 +msgid "The data presented in the table shows the cost of each service or repair. The rows represent the vendors, and each vehicle that was serviced by them appears beneath each vendor. The column represent the different service types performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:137 +msgid "The table can be inserted in a spreadsheet or downloaded. To add the pivot table to a spreadsheet in Odoo, click :guilabel:`Insert In Spreadsheet` and a pop-up appears. Select the spreadsheet the data should be added to from the drop-down menu, and click :guilabel:`Confirm`. The spreadsheet then loads on the screen. The spreadsheets are stored in Odoo's *Documents* application. To download the table in an `xlsx` format, click the :guilabel:`Download` icon." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Download the pivot table to an xlsx file, or insert the data in a spreadsheet in Odoo's\n" +"Documents application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:6 +#: ../../content/applications/hr/payroll/reporting.rst:39 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:8 +msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:12 +msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:20 +msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:23 +msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Settings available for Payroll." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:32 +msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:38 +msgid "Odoo can handle a multi-company configuration. This is generally done when there is a main company or office location, such as a headquarters, and there are other offices/branches around the country or globe, that fall under that main company or headquarters. In Odoo, each company, including the headquarters, would be setup as their own company/branch using the multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:44 +msgid "Each individual company can have a different localization setting configured for that specific company, since company locations can vary and be located anywhere in the world, where rules and laws differ. For more information on companies refer to :doc:`this documentation <../general/users/companies>` on setting up companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:52 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:54 +msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:59 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:62 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:64 +msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entries --> Work Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:72 +msgid "Each work entry type has a code to aid in the creation of payslips, and to ensure all taxes and fees are correctly entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of all work entry types currently available for use, with the payroll code and color." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:80 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:82 +msgid "To create a new :guilabel:`Work Entry Type`, click the :guilabel:`New` button, and enter the information for the following sections on the form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:86 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:88 +msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid ":guilabel:`Payroll Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:93 +msgid ":guilabel:`DMFA code`: This code is used to identify :abbr:`DMFA (De Multifunctionele Aangifte)` entries on a corresponding DMFA report. The DMFA report is a quarterly report that Belgian-based companies are required to submit for social security reporting purposes. This report states the work done by the employees during the quarter, as well as the salaries paid to those employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:97 +msgid ":guilabel:`External Code`: This code is used for exporting data to a third-party payroll service. Check with the third-party being used in order to determine the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid ":guilabel:`SDWorx code`: This code is only for companies that use SDWorx, a payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:102 +msgid ":guilabel:`Color`: Select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:107 +msgid ":guilabel:`Rounding`: The rounding method selected determines how quantities on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:110 +msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:111 +msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:115 +msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid ":guilabel:`Unpaid in Structures Types`: If the work entry is for work that is not paid, specify which pay structure the unpaid work entry applies to from the drop-down menu. Some situations where work would be logged on a timesheet but no compensation given would be for unpaid internships, unpaid training, or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:129 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:131 +msgid ":guilabel:`Meal Voucher`: If the work entry should count towards a meal voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:132 +msgid ":guilabel:`Representation Fees`: If the work entry should count towards representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:134 +msgid ":guilabel:`Private Car Reimbursement`: If the work entry should count towards a private car reimbursement, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:138 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:140 +msgid ":guilabel:`Time Off`: Check this box if the work entry type can be selected for a time off request or entry in the *Time Off* application. If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours` for example. A new type of time off can be entered in the field if the listed types of time off in the drop-down menu do not display the type of time off needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid ":guilabel:`Keep Time Off Right`: This is for Belgian-specific companies only, and will not appear for other localizations. Check this box if the work entry is for time off that will affect the time off benefits for the following year. Workers are given time off each year according to the government, and in some cases, time-off taken during a specific time period can affect how much time off the employee will receive or accrue the following year." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:153 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:155 +msgid ":guilabel:`Unforeseen Absence`: If the work entry should be visible on the unforeseen absences report, check this box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New work entry type form with all fields to be filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:163 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "To view the currently configured working schedules, go to :menuselection:`Payroll --> Configuration --> Work Entries --> Working Schedules`. The working schedules that are available for an employee's contracts and work entries are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:169 +msgid "Working schedules are company-specific. Each company must identify each type of working schedule they use." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:173 +msgid "An Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working schedule entry for each company that uses the 40-hour standard work week." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "A database with five companies that all use a standard 40-hour work week needs to have five separate 40-hour working schedules configured." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "All working schedules available to use currently set up in the database for the company." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:186 +msgid "To create a new working schedule, click the :guilabel:`New` button, and enter the information on the form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:189 +msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:193 +msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:199 +msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:202 +msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch to 2 weeks calendar` button in the top left. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New working schedule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:216 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:218 +msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:224 +msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:230 +msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Salary --> Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of all currently configured structure types available to use." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:242 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:244 +msgid "To make a new structure type, click the :guilabel:`New` button and a structure type form appears. Enter the information in the fields. Most fields are pre-populated, but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:248 +msgid ":guilabel:`Structure Type`: Enter the name for the new structure type, such as 'Employee' or 'Worker'." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid ":guilabel:`Country`: Select the country that the new structure type applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid ":guilabel:`Wage Type`: Select what type of wage the new structure type will use, either :guilabel:`Monthly Fixed Wage` or :guilabel:`Hourly Wage`. If the wage type is going to be used for salaried employees who receive the same wage every pay period, select :guilabel:`Monthly Fixed Wage`. If the wage type is going to be used for employees who receive wages based on how many hours they worked during a pay period, select :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Default Scheduled Pay`: Select the typical pay schedule for the new structure type from the drop-down menu. Options are :guilabel:`Monthly`, :guilabel:`Quarterly`, :guilabel:`Semi-annually`, :guilabel:`Annually`, :guilabel:`Weekly`, :guilabel:`Bi-weekly`, :guilabel:`Bi-monthly`. This indicates how often this type of structure type is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:261 +msgid ":guilabel:`Default Working Hours`: Select the default working hours for the new structure type from the drop-down menu. All available working hours for the currently selected company appear in the drop-down menu. The default working hours that are pre-configured in Odoo is the :guilabel:`Standard 40 hours/week` option. If the needed working hours do not appear in the list, a :ref:`new set of default working hours can be created `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:266 +msgid ":guilabel:`Regular Pay Structure`: Type in the name for the regular pay structure." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:267 +msgid ":guilabel:`Default Work Entry Type`: Select the default type of work entry the new structure type will fall under from the drop-down menu. Options include :guilabel:`Attendance`, :guilabel:`Overtime Hours`, :guilabel:`Generic Time Off`, :guilabel:`Compensatory Time Off`, :guilabel:`Home Working`, :guilabel:`Unpaid`, :guilabel:`Sick Time Off`, :guilabel:`Paid Time Off`, and :guilabel:`Out Of Contract`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New structure type form to fill out when creating a new structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:280 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:282 +msgid "To make new default working hours, type the name for the new working hours in the :guilabel:`Default Working Hours` field on the new structure type form. Click :guilabel:`Create and edit`. A default working hours form will pop up. The default working hours form has two sections, a general information section and a tab listing out all the individual working hours by day and time. When the form is filled out, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid ":guilabel:`Name`: Type in the name for the new default working hours. This should be descriptive and clear to understand, such as `Standard 20 Hours/Week`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:290 +msgid ":guilabel:`Company`: Select the company that can use these new default working hours from the drop-down menu. Keep in mind, working hours are company-specific and cannot be shard between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:293 +msgid ":guilabel:`Average Hour Per Day`: The average hours per day field will be auto-populated based on the working hours configured in the *Working Hours* tab. This entry affects resource planning, since the average daily hours affect what resources can be used, and in what quantity, per work day." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:297 +msgid ":guilabel:`Timezone`: Select the timezone that the new default working hours will be used for from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:299 +msgid ":guilabel:`Company Full Time`: Enter the number of hours per week an employee would need to work in order to be considered a full-time employee. Typically, this is approximately 40 hours, and this number affects what types of benefits an employee can receive based on their employment status (full-time vs part-time)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:303 +msgid ":guilabel:`Work Time rate`: This percentage is auto-generated based on the entry for the :guilabel:`Company Full Time` and the working hours configured in the *Working Hours* tab. This number should be between `0.00%` and `100%`, so if the percentage is above `100%`, it is an indication that the working times and/or :guilabel:`Company Full Time` hours need adjustment." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:307 +msgid ":guilabel:`Working Hours` Tab: This tab is where each day's specific working hours are listed. When a new default working hour form is created, the working hours tab is pre-populated with a default 40-hour week, with each day divided into three timed sections. Every day has morning (8:00-12:00), lunch (12:00-13:00), and evening (13:00-17:00) hours configured using a 24 hour time format. To adjust any of these hours, click on the specific field to adjust, and make the adjustment using the drop-down menus, or in the specific case of the times, type in the desired time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:316 +msgid "If the working hours are not consistent each week, and the hours are on a bi-weekly schedule instead, click the :guilabel:`Switch to 2 week calendar` button at the top of the new default working hours form. This will change the working hours tab to display two weeks of working times that can be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:322 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:324 +msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:327 +msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:331 +msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:334 +msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "All available salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:341 +msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Salary structure details for Regular Pay, listing all the specific Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:349 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:351 +msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect actions in the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:355 +msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Salary --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:358 +msgid "To make a new rule, click :guilabel:`New`. A new rule form appears. Enter the information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:361 +msgid "The required fields for a rule are:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:363 +msgid ":guilabel:`Name`: Enter a name for the rule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:364 +msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:366 +msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code to use as this will affect accounting reports and payroll processing." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:371 +msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:375 +msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Enter the information for the new rule on the new rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:385 +msgid "Rule parameters" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:388 +msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary --> Rule Parameters` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:394 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:396 +msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Salary --> Other Input Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of other input types for payroll that can be selected when creating a new entry for\n" +"a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "To create a new input type, click the :guilabel:`New` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:410 +msgid "The :guilabel:`Code` is used in the salary rules to compute payslips. If the :guilabel:`Availability in Structure` field is left blank, it indicates that the new input type is available for all payslips and is not exclusive to a specific structure." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Create a new Input Type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:419 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, :guilabel:`Resume`, and :guilabel:`Offers`) specify what benefits can be offered to an employee in their salary package." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:427 +msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:433 +msgid "Advantages" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "When offering potential employees a position, there can be certain *advantages* or benefits set in Odoo in addition to the salary to make an offer more appealing (such as extra time off, the use of a company car, reimbursement for a phone or internet, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:439 +msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Advantages`. Advantages are grouped by :guilabel:`Structure type`, and the advantage listed for a particular structure type is only available for that specific structure." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list view of all the advantages or benefits that is available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:448 +msgid "A company has two structure types, one labeled :guilabel:`Employee`, and anther labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains an advantage of using a company car, while the :guilabel:`Intern` structure type does not. Instead, the :guilabel:`Intern` structure type has a meal voucher advantage available, while the :guilabel:`Employee` structure type does not." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:454 +msgid "A person hired under the :guilabel:`Employee` structure type can use a company car, but cannot have meal vouchers. The opposite is true for someone hired under the :guilabel:`Intern` structure type. They would have meal vouchers available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:458 +msgid "To make a new advantage, click the :guilabel:`New` button, and enter the information in the fields. The required fields for an advantage are:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:461 +msgid ":guilabel:`Name`: Enter the name for the advantage." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:462 +msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:464 +msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:467 +msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:469 +msgid ":guilabel:`Display Type`: Select from the drop-down menu how this advantage is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of advantages employee's can have." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:476 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "Every employee in Odoo has an *employee card* which is created when a candidate becomes an employee. This card includes all of their personal information, resume, work information, and documents." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:482 +msgid "The personal information is gathered from the salary package configurator section that a candidate fills out after being offered a position. This personal information is then transferred to the employee card when they are hired." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:486 +msgid "To view an employee's card, go to the main :menuselection:`Employees` app dashboard, and click on the employee's card." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:490 +msgid "An employee card can be thought of as an employee personnel file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:492 +msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the personal information that appears on employee card to enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:500 +msgid "To edit a personal info entry, select the entry from the list, and modify the personal info. To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:503 +msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`. Select a :guilabel:`Related Model` from the drop-down menu. :guilabel:`Employee` populates the field by default, but the :guilabel:`Bank Account` option is also available if the information is related to a bank account instead. Select a :guilabel:`Related Field` from the drop-down menu that best describes what kind of personal information this entry is, and where it is going to be stored in the backed. Then, select a :guilabel:`Category` from the drop-down menu that the personal information should be under, such as :guilabel:`Address` or :guilabel:`Personal Documents`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:512 +msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card. The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New personal information entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "Resume" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:526 +msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator --> Resume` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:532 +msgid "Offers" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "When a candidate is offered a position, there are several items that need to be tracked in order for a business to stay organized, such as where in the offer process the candidate is, how long the offer is valid for, as well as all the offer details. These details are all stored in each *offers* record." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "To view all offers, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Offers`. All offers that have been sent to either potential candidates or current employees appears in this list. The status, offer start date and expiration date, amount of the contract, and more, can all be found in this list. Offers sent via the :guilabel:`Recruitment` application appear here, but there is an option to create a new offer from the :guilabel:`Payroll` application as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all offers given to a current employee or potential candidate along with the\n" +"status of the offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "To create a new offer, click the :guilabel:`New` button. The two required fields are the :guilabel:`Contract Template`, and the :guilabel:`Company`. Select the :guilabel:`Contract Template` and :guilabel:`Company` from the drop-down menus. Fill in any other details for the offer, such as the :guilabel:`Job Title`, :guilabel:`Department`, the :guilabel:`Contract Start Date` and the :guilabel:`Offer Validity Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:3 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, their working hours, and any other details about their position." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:10 +msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed in order to send and sign contracts. Please refer to the :doc:`/applications/finance/documents` and :doc:`/applications/finance/sign` documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Employees --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a default kanban view. The default view displays both running contracts and contracts that need action. Expired and canceled contracts are hidden in the default view." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Contracts dashboard view showing running contracts and contracts with issues." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:25 +msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application. The default contracts view in the *Payroll* application displays running contracts and contracts needing attention, while the default contracts view in the *Employees* application displays all contracts in a kanban view, organized by their stage, regardless of status. All contracts can be viewed by changing the filters." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:32 +msgid "Create a new contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:34 +msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the contracts dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "New contract form to be filled in when creating a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid ":guilabel:`Contact Reference`: Type in the name or title for the contract, such as `John Smith Contract`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:47 +msgid ":guilabel:`Company`: Select the company the contract applies to by clicking on the drop-down menu. A new company can be created by typing the name in the field, then clicking either :guilabel:`Create` to create the new company, or :guilabel:`Create and Edit` to create the new company and edit the company details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid ":guilabel:`Salary Structure Type`: Select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:54 +msgid ":guilabel:`Start Date`: The date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :guilabel:`< > (arrow)` icons, then clicking on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:57 +msgid ":guilabel:`Working Schedule`: Select one of the working schedules from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll --> Configuration --> Working Times` and either :guilabel:`Create` a new working time or click on an existing working time and edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:68 +msgid ":guilabel:`Employee`: Name of the employee that the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:69 +msgid ":guilabel:`Department`: The department the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +msgid ":guilabel:`Job Position`: The specific job position the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:71 +msgid ":guilabel:`Contract Type`: Choose from :guilabel:`CDI`, :guilabel:`CDD`, or :guilabel:`PFI` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid ":guilabel:`CDI` is an open-ended contract with only a start date but no end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:75 +msgid ":guilabel:`CDD` is a contract with both a start date and an end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:76 +msgid ":guilabel:`PFI` is a Belgian-specific contract used when hiring employees that need training, and covers the training period specifically." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:79 +msgid ":guilabel:`End Date`: If the contract has a specific end date, click the drop-down menu, navigate to the correct month and year using the arrow icons, then click on the date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:81 +msgid ":guilabel:`HR Responsible`: If there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid ":guilabel:`Analytic Account`: This field allows a link between the contract and a specific analytic account for accounting purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:87 +msgid "Contract details" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:89 +msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Contract details in optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:96 +msgid ":guilabel:`Contract Template`: Select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:98 +msgid ":guilabel:`New Contract Document Template`: Select a contract from the drop-down menu to be modified for this new employee contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:100 +msgid ":guilabel:`Contract Update Document Template`: Select a contract from the drop-down menu if the employee has an existing contract that requires updating." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid ":guilabel:`Notes`: The notes field is a text field where any notes for the employee contract can be entered for future reference." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:106 +msgid "Modifying a contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:108 +msgid "Click the :guilabel:`External Link` button at the end of each line to open the corresponding contract template and make any changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:115 +msgid "A pop-up window appears with all the contract details. Modify the fields for the contract as needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Edit the details for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:121 +msgid ":guilabel:`Tags`: Select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:122 +msgid ":guilabel:`Signed Document Workspace`: This is where the signatures are stored. Choose a pre-configured workspace or create a new one." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:124 +msgid ":guilabel:`Signed Document Tags`: Select or create any tags associated only with the signed contract as opposed to the original unsigned contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid ":guilabel:`Redirect Link`: Enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another, in this case, to the newly updated contract specifically written for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:129 +msgid ":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or :guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:131 +msgid ":guilabel:`All Users`: Any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:132 +msgid ":guilabel:`On Invitation`: Only users selected in this field can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:134 +msgid ":guilabel:`Invited Users`: Select the person(s) that can sign the document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid ":guilabel:`Document`: The attached document can be replaced by clicking the :guilabel:`✏️ (pencil)` icon. A pop-up window appears so another document can be selected for upload. The file must be a PDF. To remove the document, click the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "Once the edits are complete, click the :guilabel:`Save` button. All the information for the selected contract template populates the fields in the :guilabel:`Salary Information` tab. Any additional tabs, such as :guilabel:`Personal Documents`, appears if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "Salary information" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:150 +msgid "This section is where the specific salary details are defined. This section is country-specific, so depending on where the company is located, these fields may vary." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "Enter the amount in the various fields, or check a box to apply a benefit. Some options that can be entered here include :guilabel:`Meal Vouchers`, :guilabel:`Fuel Card`, :guilabel:`Internet`, :guilabel:`Paid Time Off`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Some fields may be automatically filled in based off of the contracts selected in the :guilabel:`Contract Details` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:161 +msgid "Attachment of salary" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:163 +msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. This section is where all of these deductions or allocations are set." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:167 +msgid "To add a new deduction, click :guilabel:`Add a line`. Type in a description for the allocation under :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Enter a new line for each type of garnishment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:174 +msgid "Select the :guilabel:`Garnished Type` from the drop-down menu. Choose from:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:176 +msgid ":guilabel:`Attachment of Salary`: Any payments taken out towards something that is *not* child support. Typically any garnishments such as lawsuit payments, payments toward taxes owed, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:178 +msgid ":guilabel:`Assignment of Salary`: Any deduction that is not required but voluntary, such as a pre-tax allocation to a college savings account." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:180 +msgid ":guilabel:`Child Support`: Any payments taken out specifically for child support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:182 +msgid "Enter the start and end dates the entry applies to. Click on the drop-down menu under :guilabel:`From` and :guilabel:`To`, navigate to the correct month and year by using the :guilabel:`< > (arrow)` icons, then click on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:186 +msgid "Last, enter the :guilabel:`Amount` that each payslip pays towards the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:188 +msgid "To delete a line, click the :guilabel:`🗑️ (trash can)` icon at the end of the line." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:191 +msgid "Save and send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "Once a contract has been created and/or modified, save the contract by clicking the :guilabel:`Save` button. Next, the contract must be sent to the employee to be signed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:196 +msgid "Click on one of the following buttons to send the contract to the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Send the contract to the employee via one of the buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid ":guilabel:`Generate Simulation Link`: This option is for Belgian companies only. Clicking this opens a pop-up window that contains the basic information from the contract as well as a link for the contract when using the salary configurator. Click :guilabel:`Send Offer` to send an email to the employee so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Sends a link to the employee for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:212 +msgid "In order to send a contract using the :guilabel:`Generate Simulation Link`, there must be a signature field in the contract PDF being sent to the employee so they can sign it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:215 +msgid ":guilabel:`Signature Request`: Click this and a pop-up window appears where an email can be typed to the employee. Select the document, such as a contract, NDA, or Homeworking Policy, from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Request a signature for the contract via email." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:224 +msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "Payslips are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:10 +msgid "The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` application consists of three sections: :guilabel:`To Pay`, :guilabel:`All Payslips`, and :guilabel:`Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:13 +msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Payslips menu selection in Payroll." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:21 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:23 +msgid "Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the payslips that need to be paid. On this page, Odoo displays the payslips that have not been generated yet, and can be created from this dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View all payslips that need to be paid on the Payslips To Pay page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:31 +msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:36 +msgid "Clicking on an individual payslip entry will show the details for the individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:41 +msgid "Create new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:47 +msgid "Clicking :guilabel:`Create` reveals a blank payslip form, wherein the necessary payslip information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The necessary fields for a new payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:60 +msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:66 +msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:70 +msgid ":guilabel:`Contract`: Using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:72 +msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:75 +msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The necessary fields for a new payslip in the Accounting Information tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:87 +msgid "It is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:93 +msgid ":guilabel:`Reference`: Any note or reference message for the new entry can be entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:94 +msgid ":guilabel:`Company Car`: If applicable, select the company car from the drop-down." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:95 +msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:100 msgid ":guilabel:`Salary Computation`: The :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays all the wages, deductions, taxes, etc. for the entry." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:103 -msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu." +#: ../../content/applications/hr/payroll/payslips.rst:103 +msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:105 +msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:109 +msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:112 +msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:116 +msgid "Save and process new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:118 +msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:126 +msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:132 +msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel Payslip` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The new payslip is emailed to the employee and the email appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:143 +msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click Make Payment to send the payment to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:152 +msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:156 +msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "Banking information can be entered in an employee's card." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:167 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:169 +msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:172 +msgid "Click on the :guilabel:`▶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:179 +msgid ":guilabel:`Draft` indicates the payslip is created, and there is still time to make edits, since the amounts are not calculated." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:181 +msgid "`Waiting` indicates the payslip has been calculated and the salary details can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:183 +msgid "`Done` indicates the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View all payslips organized by batches. Click on the arrow to expand each batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:189 +msgid "Click on an individual payslip to view the details for that payslip on a separate page. Using the breadcrumb menu, click :guilabel:`Employee Payslips` to go back to the list view of all payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:192 +msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create a new payslip ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:197 +msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click on the Print smart button to print payslips to a PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:206 +msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click on the Export All smart button to export all payslips to an Excel payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:218 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:220 +msgid "To view payslips in batches, navigate to :menuselection:`Payroll app --> Payslips --> Batches` to display all the payslip batches that have been created. These payslip batches are displayed in a list view, by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:224 +msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View displaying all batches created." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:231 +msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:235 +msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:242 +msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:247 +msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Generate payslips from the edited batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:256 +msgid "Back on the batch details page, click the :guilabel:`Create Draft Entry` smart button to create a draft of the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:263 +msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:268 +msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:272 +msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click the Payslips smart button to view the individual payslips in the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:280 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:282 +msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:286 +msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`▼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:299 +msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:301 +msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:304 +msgid "To create the payslips for the newly-created batch, click the :guilabel:`Generate Payslips` button at the top of the form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:307 +msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`✖ (x mark)` icon at the far right of the payslip line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:311 +msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "Click the :guilabel:`Generate` button at the bottom of the pop-up window to create the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Generate payslips for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:322 +msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:326 +msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`✖ (x mark)` icon can be clicked to close the alert." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:330 +msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:335 +msgid "From here, click the :guilabel:`Generate Draft Entry` button to change the payslips' status from :guilabel:`Draft` to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:338 +msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "When done, click the :guilabel:`Confirm` button to confirm the information, or click :guilabel:`Cancel` to discard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "Generate commission payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:349 +msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:354 +msgid "Doing so reveals a :guilabel:`Generate Commission Payslip` pop-up window, in which the necessary information **must** be filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the commission details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:361 +msgid "On this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrows, navigate to the correct month, and click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:366 +msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:368 +msgid "When a department is selected, the employees listed for that department appear in the :guilabel:`Employee` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:371 +msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +msgid "Add a new entry by clicking :guilabel:`Add a Line`, and entering the :guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:378 +msgid "Click the :guilabel:`Upload Your File` button to add a file, if necessary. Any file type is accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:381 +msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:385 +msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "The :guilabel:`Reporting` section of the *Payroll* app offers a variety of reports to choose from. The :guilabel:`Payroll`, :guilabel:`Meal Vouchers`, :guilabel:`Attachment of Salary`, and :guilabel:`DMFA` reports are universal and available for all companies regardless of location. The :guilabel:`Paid Time Off Allocation`, :guilabel:`273S Sheet`, and :guilabel:`274.XX Sheets` reports are specific to Belgian companies only." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "To view a report, go to :menuselection:`Payroll --> Reporting` and click on the specific report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:17 +msgid "If a report is unavailable to a company, a user error pops up, stating `You must be logged in to a Belgian company to use this feature.`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:20 +msgid "At the top of each report, click on :guilabel:`Filters` to display the optional filters for the specific report. Filters show information that matches the specific filter parameters. For example, when selecting the :guilabel:`Last 365 Day Payslip` filter, only payslips for the last 365 days appear. All reports have the option to add a custom filter, and each have different default custom filter options. Select the parameters, then click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:30 +msgid "Clicking on :guilabel:`Favorites` displays three options: :guilabel:`Save the current search`, :guilabel:`Add the search to the dashboard`, or :guilabel:`Insert the search to a Google spreadsheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Favorite options for reports." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "Click on :menuselection:`Payroll --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid "This shows all the payslips generated in the last 365 days. The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various options to display. The options available include: :guilabel:`# Payslip`, :guilabel:`Basic Wage`, :guilabel:`Basic Wage for Time Off`, :guilabel:`Days of Paid Time Off`, :guilabel:`Days of Unforeseen Absence`, :guilabel:`Days of Unpaid Time Off`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, :guilabel:`Work Days`, :guilabel:`Work Hours`, and :guilabel:`Count`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:61 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:63 +msgid "A line chart is the default view for the *Payroll Analysis* report. If a different view was selected, click on the :guilabel:`Line Chart` icon (middle icon) in the menu bar to change the view back to a line chart. An option to display the line chart in ascending or descending order appears at the end of the options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:73 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:75 +msgid "To display the data in a bar chart, click on the :guilabel:`Bar Chart` icon (first icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:82 +msgid "Click the :guilabel:`Stacked` icon to view the bar chart in a stacked format (where multiple values appear in each column). An option to display the columns in ascending or descending order appears at the end of the options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:87 +msgid "Clicking an option enables it. To disable the option, click it again. When the option is enabled it appears grey. When it is inactive, it appears white." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:91 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:93 +msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` icon (last icon) in the menu bar. There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:101 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:103 +msgid "The bottom half of the :guilabel:`Payroll Analysis` dashboard presents a pivot table no matter which type of chart is selected for the top of the dashboard. The default information displayed is the number of payslips, net wage, gross wage, days of paid time off, and days of unpaid time off. The information is divided by department. To display more information on the report, select the :guilabel:`Measures` drop-down menu, then click on any other items to display." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:113 +msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, click on the column name twice. The first click selects the column, and the second click sorts the information in descending order." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "To sort information by descending order, click the column head twice." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:121 +#: ../../content/applications/hr/payroll/reporting.rst:172 +msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` icon. The information will be downloaded into an Excel spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Download an Excel spreadsheet of the data by clicking the download button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:128 +#: ../../content/applications/hr/payroll/reporting.rst:179 +msgid "The data can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A pop-up appears asking which spreadsheet to place the information in. Select an existing spreadsheet or enter the name for a new spreadsheet. Click the :guilabel:`Confirm` button to move to a spreadsheet view with all the information populated." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Send the data to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:137 +msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the setting as a template to use in the future." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:141 +#: ../../content/applications/hr/payroll/reporting.rst:188 +msgid "The *Documents* application must be installed in order to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:146 +msgid "Meal Vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:148 +msgid ":guilabel:`Meal Vouchers` provides an overview of the meal vouchers used by employees, and can be shown by :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`. The default view is by month." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Meal voucher" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +msgid "To change the displayed view, click on :guilabel:`Total`. The data collapses, showing only the count column. Click on :guilabel:`Total` again, then hover over :guilabel:`Day`, then click on one of the other time-period options available." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:164 +msgid "It is possible to compare the current meal voucher report to the one for the previous time period or the previous year. To view these comparisons, click on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Date: Previous Period` or :guilabel:`Date: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the settings as a template to use in the future." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "Attachment of Salary" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "The :guilabel:`Attachment of Salary` report shows all deductions or allocations per employee, such as child support payments and wage garnishments." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "View the Attachment of Salary report that shows all salary garnishments." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:201 +msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by month." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:204 +msgid "The report can be exported as a XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "Clicking on the :guilabel:`Measures` button shows options for how the data is displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count`, can all be selected or deselected by clicking on the item. If an item has a check mark, it is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Select the options that be displayed in the report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "The salary attachment report can be compared to the one for the previous time period or the previous year. To view these comparisons, click on the on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Work Entries dashboard view showing all employee's work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:13 +msgid "To change the view so that only the entries for a single day, week, or month are shown, click on one of the corresponding links for :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`, located at the top of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:17 +msgid "Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons on the left and right side of the :guilabel:`Today` button to adjust the displayed dates. The arrows will adjust the date based on the type of time selected. For example, if month is selected, the arrows will move one month with each click of the arrow. If week or day is selected, the time will move by either a week or a day for each click of the arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:24 +msgid "Adding a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:26 +msgid "If a work entry is missing and needs to be added, such as sick time or time off, click :guilabel:`Add` to create a new work entry. A pop-up will appear, with several fields to fill in." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:29 +msgid "Enter the :guilabel:`Work Entry Name`, such as `Sick Time` or any other short description. Select the :guilabel:`Employee` and the :guilabel:`Work Entry Type` from the respective drop-down lists." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Filling in the work entry Create form in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:36 +msgid "Next, enter the date and time for the work entry in the :guilabel:`From` and :guilabel:`To` drop-downs. First, select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:40 +msgid "Then, select the time by clicking on the :guilabel:`⏰ (clock)` icon, and using the :guilabel:`⬆️ (up arrow)` and :guilabel:`⬇️ (down arrow)` icons for each section to enter the hour, minute, and second for the time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:44 +msgid "The :guilabel:`Period` will display the hours based on the :guilabel:`To` and :guilabel:`From` entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Before clicking either :guilabel:`Save & Close` or :guilabel:`Save & New`, it is good to double check the :guilabel:`Period` to ensure the time stated corresponds to the :guilabel:`To` and :guilabel:`From` fields." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:0 +msgid "Hours entered in the Period field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:56 +msgid "Once the information is entered, click :guilabel:`Save & Close` to save the entry and close the pop-up, or :guilabel:`Save & New` to save the entry and create another :guilabel:`Work Entry Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:60 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "After a work entry has been either added or modified, the work entries need to be regenerated for the affected employee(s). Click on the :guilabel:`Regenerate Work Entries` button at the top of the main dashboard, and a pop-up will appear." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:66 +msgid "Select the :guilabel:`Employee` to regenerate work entries for from the :guilabel:`drop-down menu`, and adjust the :guilabel:`From` and :guilabel:`To` fields so the correct date range is displayed. Click the :guilabel:`Regenerate Work Entries` button and the work entries will be recreated. Once finished, the pop-up will close." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate a work entry for a particular employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:76 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:78 +msgid "A conflict appears for any request that has not been approved, such as sick time or vacation, or if there are any errors on the work entry, such as required fields being left blank. Conflicts are required to be resolved before payslips can be generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:82 +msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` overview dashboard, located by going to :menuselection:`Payroll --> Work Entries --> Conflicts`, where only conflicts needing resolution are shown." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Conflicts dashboard view showing all employee's conflicts in work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:90 +msgid "Conflicts are indicated with an orange triangle in the top left corner of each individual entry. Click on an individual work entry to see the conflict details in a pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:93 +msgid "The conflict is briefly explained in an orange text box." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Details for a conflict appear in the pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "The :guilabel:`Work Entry Name`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up. The :guilabel:`From` and :guilabel:`To` date range, as well as the total time requested (in hours), appear in the :guilabel:`Period` field on the right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:103 +msgid "If there is a conflict because a time-off request for the same time already exists in the system, the time-off will be entered in the :guilabel:`Time Off` field. Clicking the :guilabel:`External Link` button next to the :guilabel:`Time Off` entry will bring up the duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "The details for the time-off request appear in the pop-up. The request can be modified if needed. Click either the :guilabel:`Validate` or :guilabel:`Refuse` button to approve or deny the request, then click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Edit and/or validate a duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:115 +msgid "Once the duplicate time-off request has been approved and saved, the screen goes back to the conflict. Click :guilabel:`Refuse Time Off` or :guilabel:`Approve Time Off` via the buttons in the top right to either approve or deny the request. Repeat for all conflicts until there are no conflicts to resolve." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:120 +msgid "After conflicts have been resolved, work entries must be regenerated for each employee by clicking the :guilabel:`Regenerate Work Entries` button, and entering the corresponding information for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate Work Entries button on the Work Entries Regeneration form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:129 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "To generate payslips, navigate to the time period the payslips should be generated for, either day, week, or month. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Generate Payslips button on the Work Entry dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "If the :guilabel:`Generate Payslips` button is not active (appears light turquoise instead of dark turquoise), that indicates there are conflicts. *Solve conflicts first* will appear as a warning when :guilabel:`Generate Payslips` is moused over. Resolve all conflicts before generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "A batch entry will appear for the time period selected. The batch name appears at the top in the :guilabel:`Name` field, typically listing the month and year for the particular batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:148 +msgid "The date range the payslips apply to appears in the :guilabel:`Period` field. The company appears in the :guilabel:`Company` field, along with an option to mark the payslips as a credit note. To make changes, click the :guilabel:`Edit` button in the top left, make any changes, then click either :guilabel:`Save` to accept the changes or :guilabel:`Discard` to revert to the original data." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Batch information that appears when making a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:157 +msgid "Click the :guilabel:`Create Draft Entry` button to create the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:159 +msgid "Click on the :guilabel:`Payslips` button in the top right to view all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:162 +msgid "Payslips will have a status of *Waiting* until the :guilabel:`Create Draft Entry` button has been clicked. After, the payslip status will change to *Done*." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:165 +msgid "Payslips can be printed by clicking the box next to each payslip to print, or clicking the box next to :guilabel:`Reference` to select all the payslips at once. Click the :guilabel:`Print` button, and a PDF file will be created with all the specified payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Print button for printing the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:174 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:6 +#: ../../content/applications/hr/recruitment/new_job.rst:51 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:8 +msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, to sending a job offer, just to name a few. This process is referred to as the 'applicant flow'." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:13 +msgid "When an applicant applies for a job position, an *applicant card* is automatically created in Odoo's *Recruitment* app for that specific job position. As the applicant progresses through the recruitment pipeline, the recruitment team moves their card from one stage to the next." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:17 +msgid ":ref:`Stages can be configured ` so that an email is automatically sent out using a set, pre-configured template as soon as an applicant's card enters a stage. These automated emails are defined on each stage in the applicant flow." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:21 +msgid "The applicant flow explained in this document is the default flow in Odoo, and goes through the applicant flow when using the *Recruitment* application's default configuration. The applicant flow is able to be modified to suit the specific recruitment flow for any business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:26 +msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes will be visible on all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:35 +msgid "To access the kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`New Applications` smart button on a job position card to navigate to the kanban view for all the applicants for that particular job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Main dashboard view of job position card, showing new applications button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "Inside the job application, the kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are five default stages in Odoo:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:49 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:50 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid ":ref:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:52 +msgid ":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:54 +msgid "The last column, :guilabel:`Contract Signed`, is folded by default, meaning that the column appears in gray and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Expand a folded column by clicking on it in the kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:63 +msgid "Each stage has a color-coded bar beneath the stage name, giving information about the applicant's status in the stage. The colors are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid ":guilabel:`Green`: there are applicants in the stage with an activity that is either already scheduled or needs to be scheduled in the future (such as a phone call or interview), according to the parameters for that particular stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:69 +msgid ":guilabel:`Yellow`: there are applicants in the stage with an activity either scheduled for today or due to be scheduled today." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:71 +msgid ":guilabel:`Red`: there are applicants in the stage with overdue activities which need to be scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:73 +msgid ":guilabel:`Gray`: there are either no activities currently scheduled and no future activities that are required to be scheduled, or there are no applicants currently in the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:79 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:85 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid "To create a new stage, click on :guilabel:`+ Add a Column` and a new column appears. Enter the title for the new stage in the :guilabel:`Column title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new column creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click in order to add a new column to the kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:99 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:101 +msgid "To modify the settings of a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears in the upper right hand side of the stage. Click on the :guilabel:`⚙️ (gear)` icon and a menu appears. Then click on the :guilabel:`Edit Stage` option. An :guilabel:`Edit Column` form appears. Make any modifications to the form, then click :guilabel:`Save` when done." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The gear icon that appears when a column name is moused over, and the drop-down menu it\n" +"displays when clicked." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:112 +msgid "Edit column form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "The :guilabel:`Edit Column` form is where the stage's settings are configured. The only required fields are the :guilabel:`Stage Name`, and the :guilabel:`Tooltips` section." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:117 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid ":guilabel:`Stage Name`: type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:120 +msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email will automatically be sent to the applicant using the selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:123 +msgid ":guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times in the default view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:125 +msgid ":guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper right corner. If this box is checked, this stage is used to determine the hire date of an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:129 +msgid ":guilabel:`Job Specific`: if the stage only applies to a specific job position(s), select the job position(s) from the drop-down menu. Multiple job positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:131 +msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:135 +msgid ":guilabel:`Tooltips` section: there are three pre-configured labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +msgid ":guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:144 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:146 +msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears. First, click on the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A pop-up warning appears, asking :guilabel:`Are you sure you want to remove this column?`. Click :guilabel:`OK` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage, explaining that there are records in the stage which need to be deleted, archived, or moved to a different stage before deleting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:157 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:159 +msgid "To communicate with the applicant, Odoo has several pre-configured email templates that can be used. The pre-configured email templates and when to use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid ":guilabel:`Applicant: Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid ":guilabel:`Applicant: Interest`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid ":guilabel:`Applicant: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:171 +msgid ":guilabel:`Applicant: Refuse`: this template is used when an applicant is no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid ":guilabel:`Applicant: Your Salary Package`: this template is used when offering an applicant a position. This informs the applicant they can configure their salary package." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/email_communication/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:181 +msgid "To manually send an email click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address. Click the :guilabel:`⤢ (double arrow)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:189 +msgid "An email composer pop-up loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered on the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `Re: (Subject / Application Name)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:193 +msgid "To use a pre-configured email template, click the drop-down next to the :guilabel:`Load template` field in the lower right section of the window. Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid "Only the email templates that are configured for the model will load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they will not appear in the list of available templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "If any attachments are to be added, click the :guilabel:`Attach A File` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :guilabel:`X (Delete)` icon to the right of the attachment. If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save As New Template` button in the bottom right corner. To send the email, click :guilabel:`Send` and the email will be sent to the applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:213 +msgid "Stage flow" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the kanban view to the desired stage, or the stage can be modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:219 +msgid "To change the stage on the applicant's card, click on the applicant's card in the kanban view to go to a detailed view of the card. The current stage for the card is highlighted in purple at the top, above the card. Simply click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top left, and the applicant's card now appears in the new stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Change the stage of an applicant by clicking on the desired stage at the top of the\n" +"applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:237 +msgid "The following information is based on Odoo's default recruitment pipeline flow. Be advised that if modifications are made to create a customized recruitment pipeline flow, it will vary from the following information." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "All applicants appear in the :guilabel:`Initial Qualification` stage, whether submitted online or if the applicant is manually entered by a recruiter. When the applicant's card is created, Odoo automatically populates the applicant's :guilabel:`Name`, :guilabel:`Email address`, and :guilabel:`Phone number` on the applicant's card. This information is required when applying for a job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:247 +msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it is populated in the :guilabel:`Application Summary` tab at the bottom of the applicant's card. If a resumé was attached to the online application, the resumé appears in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the Documents application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the right side. All recruitment documents will be stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:256 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:258 +msgid "At any point in the hiring process, an *interview* can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:261 +msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job position's needs. For example, a job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:270 +msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, the applicant's card appears instead of the :guilabel:`Survey` pop-up window. Enter the email address in the email field, then click :guilabel:`Save`. Once the applicant's card is saved, the applicant's card closes and the :guilabel:`Survey` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:276 +msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, click the button labeled :guilabel:`Send Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:280 +msgid "If the applicant's card has an email address on file, a :guilabel:`Survey` pop-up window appears, with all the information populated. If an email is not on the applicant's card, then a contact form appears. Enter the applicants email address, then click :guilabel:`Save`. The card closes and the :guilabel:`Survey` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:285 +msgid "Odoo refers to the interview forms as *surveys*. These email templates also use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact on the :guilabel:`Recipients` line. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email to the :guilabel:`Additional emails` line." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:292 +msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:296 +msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "The :guilabel:`Mail template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:306 +msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"pre-configured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:315 +msgid "Refuse" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:317 +msgid "At any point in the recruitment pipeline, an applicant can be refused from the job application process. To refuse an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:322 +msgid "A :guilabel:`Refuse Reason` pop-up appears. Select the :guilabel:`Refuse Reason` from the drop-down menu. The default refuse reasons in Odoo are: :guilabel:`Doesn't fit the job requirements`, :guilabel:`The applicant is not interested anymore`, and :guilabel:`The applicant gets a better offer`. These three refusal reasons have pre-configured email templates associated with them. Additional refusal reasons can be created and existing ones can be modified or deleted. To add a new refusal reason, type in the name of the reason, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Refuse Reason` pop-up window appears. Type in the name of the new email template in the :guilabel:`Email Template` field, and click :guilabel:`Create and Edit...`. A :guilabel:`Create: Email Template` window loads. Configure the new email template, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:334 +msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name will appear anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/email_communication/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:340 +msgid "An email template populates the :guilabel:`Email Template` field after a refusal reason is selected. If an email should not be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox. To view the email template, click the :guilabel:`External Link` icon to the right of the email template selected. The email template loads in the pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save`. To close the email template, click :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:346 +msgid "To send the refusal email to the applicant, click :guilabel:`Send`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card with the refused banner appearing in the top right corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "After refusal, the applicant's card is no longer visible in the job position's kanban view. To view refused applicants, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. All applications for all job positions are presented in a list view. To view the refused applicants only, click :guilabel:`Filters`, then click :guilabel:`Archived/Refused`. All applicants that have been archived and/or refused appear in the list. To further organize this list and view refusals by job position, click :guilabel:`≣ Group By`, then click :guilabel:`Job`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:361 +msgid "New applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online yet) an applicant card can be easily added from the job position kanban view in one of two ways, using either the :ref:`Quick add ` icon or the :ref:`Create ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:374 +msgid "Quickly add a new applicant using the :guilabel:`Quick add` icon. If not already in the job position kanban view, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click on the small :guilabel:`+ (plus sign) Quick add` icon in the top right of the :guilabel:`Initial Qualification` stage to quickly add a new applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered when using the Quick Add option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:384 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:386 +msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view (unless in the Developer mode), but is visible on the individual card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +#: ../../content/applications/hr/recruitment.rst:435 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +#: ../../content/applications/hr/recruitment.rst:436 +msgid ":guilabel:`Email`: enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card will appear in the selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :guilabel:`🗑️ (delete)` icon or click anywhere on the screen to close the card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:401 +msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `, then click :guilabel:`Save`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:408 +msgid "Create" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:410 +msgid "Add a new applicant including all the relevant information using the :guilabel:`Create` button. If not already in the kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click the :guilabel:`Create` button in the top left of the kanban view and an applicant form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:416 +msgid "Certain fields on the applicant card may be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are all pre-populated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:420 +msgid "Enter the following information on the new applicant form. Note that not all fields listed below may be visible. Depending on installed applications and configurations, some fields may not be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:427 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:429 +msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:437 +msgid ":guilabel:`Phone`: enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:438 +msgid ":guilabel:`Mobile`: enter the applicant's mobile number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:439 +msgid ":guilabel:`Degree`: select the applicant's highest level of education earned from the drop-down menu. Options are :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates graduating the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:444 +msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, the click :guilabel:`Create \"new tag\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:446 +msgid ":guilabel:`Interviewer`: select the person who will be conducting the interview(s) from the drop-down menu. The person must have either *recruiter* or *officer* rights configured for the Recruitment application in order to appear on the drop-down." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:449 +msgid ":guilabel:`Recruiter`: select the person responsible for the entire recruitment process for the job position. Only *users* can be selected, and all users are presented in the drop-down to select from." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:452 +msgid ":guilabel:`Appreciation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:455 +msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:460 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:462 +msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the Job Position. Editing the fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:465 +msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:467 +msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:469 +msgid ":guilabel:`Company`: select the company the job positions is for using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:472 +msgid "Contract section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:474 +msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:477 +msgid ":guilabel:`Expected Salary - Extra advantages...`: if any extra advantages are requested by the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:480 +msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:482 +msgid ":guilabel:`Proposed Salary - Extra advantages...`: if any extra advantages are offered to the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:485 +msgid ":guilabel:`Availability`: using the calendar module in the drop-down menu, select the available start date for the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:489 +msgid "Application summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:491 +msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:501 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:503 +msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card moves from one stage t another by using the click and drag method." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:512 +msgid "When the applicant's card moves to the :guilabel:`First Interview` stage, an acknowledgement email is automatically sent to the applicant. The email is created using an email template titled :guilabel:`Applicant: Acknowledgement`. This email template is pre-configured in Odoo, and contains dynamic placeholders for the job position, the recruiter's name, and the company's information. Once the email is sent, the email appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:521 +msgid "Schedule a meeting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:523 +msgid "When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:527 +msgid "The applicant's card can be found by navigating to the :menuselection:`Recruitment application` dashboard, click on a :guilabel:`New Applications` button in the job position card, then click on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:532 +msgid "The meeting smart button will display :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this will be the default. If there are any meetings already scheduled, the smart button will display :guilabel:`Next Meeting` with the date of the upcoming meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:537 +msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees will be visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:543 +msgid "The default view is the week view. To change the calendar view, click on a button to present the calendar in a different view, either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`. To change the displayed date range for the calendar, either use the :guilabel:`⬅️ (Left)`, :guilabel:`➡️ (Right)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:553 +msgid "To add a meeting to the calendar, click on the day the meeting is to take place, or click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. If the calendar is displaying the day or week view, click on the day *and* the time slot the meeting is to take place. A :guilabel:`New Event` pop up appears, with the :guilabel:`Meeting Subject` populated with the applicant card's :guilabel:`Subject/Application Name`. The default time slot is 30 minutes. If the information is correct, click :guilabel:`Create` to add the meeting to the calendar, or click :guilabel:`Edit` to modify the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:561 +msgid "If :guilabel:`Edit` is clicked, an expanded :guilabel:`New Event` card loads. Make any changes needed to the form." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:565 +msgid "New event card" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:567 +msgid "The fields available to populate or modify on the detailed :guilabel:`New Event` card are as follows. The only required fields to enter are the :guilabel:`Meeting Subject`, :guilabel:`Starting At`, and :guilabel:`Ending At` fields. Once the card details are entered, click :guilabel:`Save` to save the changes and create the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:572 +msgid ":guilabel:`Meeting Subject`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:575 +msgid ":guilabel:`Attendees`: select the people who should be in attendance. The default employee listed is the person who is creating the meeting. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:579 +msgid "Meeting details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:581 +msgid ":guilabel:`Starting At`: using the drop-down calendar, select the date and time for the meeting start time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:583 +msgid ":guilabel:`Ending At`: using the drop-down calendar, select the date and time for the meeting end time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:585 +msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:588 +msgid ":guilabel:`All Day`: if the meeting is an all day long event, check the box next to :guilabel:`All Day`. After this box is checked, the :guilabel:`Duration` field is hidden from view, a well as the meeting start and end times." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:591 +msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:593 +msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, as well as links, photos, and more. Use the powerbox feature, by typing a `/`, and a list of options are presented. Scroll through the options and click on the desired item. The item appears in the field and can be modified. Each command presents a different pop-up window. Follow the instructions for each command to complete the entry." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:599 +msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen will alert the meeting participants of the meeting via the selected option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:603 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:604 +msgid ":guilabel:`Meeting URL`: if the meeting is virtual, enter the meeting link in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:605 +msgid ":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down menu. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:609 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:611 +msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. This reveals a recurrence section. Enter the details for how often the meeting should repeat, including an end time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:614 +msgid ":guilabel:`Privacy`: select the visibility of this meeting. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:619 +msgid ":guilabel:`Show as`: select from the drop-down whether the meeting time should appear as :guilabel:`Busy` or :guilabel:`Available` in the attendees' schedules. Setting this field to :guilabel:`Available` allows other meetings to be scheduled for the same time. It is recommended to set this field to :guilabel:`Busy`, so no other meetings can be scheduled for the attendees at the same time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:630 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:632 +msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:635 +msgid "To send the meeting via email, click the :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attach A File` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:648 +msgid "To send the meeting via text message, click the :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears. At the top, in a blue box, information appears regarding the message. The first line lists how many records (phone numbers) are selected. The second line lists the number of recipients and how many of them are invalid. If a contact does not have a valid phone number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:656 +msgid "It is *not* recommended to check the box to send to all the records in the :guilabel:`Send SMS Text Message` pop-up. This would send a message to all contacts with a valid phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:659 +msgid "When the message reads :guilabel:`0 are invalid`, type in the message to be sent in the :guilabel:`Message` field. Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:670 +msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../general/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:677 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:679 +msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:684 +msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage, unlike for the :guilabel:`First Interview` stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as for the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:692 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:694 +msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top right of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:699 +msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. All fields are pre-populated with information from the job position, except for the :guilabel:`Force New Cars List`, :guilabel:`Default Vehicle`, and the :guilabel:`Canteen Cost` (this is set to `0.00`)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:706 +msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, the fields related to vehicles will not appear on the pop-up." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:712 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:714 +msgid "The following fields appear for all offers sent to applicants regardless of localization settings." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:716 +msgid ":guilabel:`Offer Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up. To modify the template, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:719 +msgid ":guilabel:`Job Title`: the name of the position being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:720 +msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:724 +msgid ":guilabel:`Yearly Cost`: the annual salary being offered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:725 +msgid ":guilabel:`Offer Link`: this link takes the applicant to a webpage where they can enter their personal information, which will be imported to their employee record when created. If applicable, the applicant can modify their salary package (this option is not available for all localizations). Lastly, this is where the applicant accepts the offer by clicking :guilabel:`Review Contract & Sign` to accept the contract and sign it using the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:733 +msgid "The *Sign* application must be installed in order for a document to be signed. Ensure the *Sign* application is installed to use this feature." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:739 +msgid "The following fields will only appear if specific localization settings are selected, and/or certain applications are installed. For example if the *Fleet* application is not installed, none of the optional fields related to vehicles will appear, such as :guilabel:`Force New Cars List` or :guilabel:`Default Vehicle`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:744 +msgid ":guilabel:`Job Position`: the official title of the job being offered to the applicant, from the :guilabel:`Job Position` card. To modify the name, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:747 +msgid ":guilabel:`Department`: the department the job position falls under. To modify the department, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:750 +msgid ":guilabel:`Force New Cars List`: check this box to offer a new vehicle to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:751 +msgid ":guilabel:`Default Vehicle`: using the drop-down menu, select the vehicle that will be assigned to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:753 +msgid ":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant for the cafeteria." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:754 +msgid ":guilabel:`Contract Type`: using the drop-down menu, select the type of contract that is being offered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Format the offer to send to the applicant. Make any modifications before sending." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:762 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:764 +msgid "To send the offer to the applicant, click :guilabel:`Send`. If the applicant does not have an email address listed on their applicant card, the applicant form appears so their email can be configured. If there is already an email configured on the applicant's card, the email pop-up appears instead. If prompted with the applicant's card, enter the applicant's email address in the :guilabel:`Email` field, then click :guilabel:`Save`. The applicant form closes and the email pop-up appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:770 +msgid "The :guilabel:`Applicant: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template. If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button. Once the email is ready to send, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:778 +msgid "To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can be sent to the applicant by the recruiter. The applicant does not need any software installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:788 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:790 +msgid "Once the applicant has accepted the offer and signed the contract, the next step is to move the applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract Signed`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:797 +msgid "The :guilabel:`Contract Signed` stage is folded in the kanban view, but the card may still be dragged and dropped into that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:800 +msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`Hired` banner appears in the top right of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Hired banner in the top right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:808 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:810 +msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:815 +msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, click :guilabel:`Save`. The employee record is now saved in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "In the default :menuselection:`Recruitment` dashboard view, all job positions are shown, regardless of status. Current published positions with active applicants are shown, as well as job positions that have been created but have not yet been published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:9 +msgid "Each job position is shown in an individual kanban card. If the job position is active and candidates can apply, then a :guilabel:`Published` banner will appear in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:13 +msgid "View submitted applications by clicking anywhere on a job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Main dashboard view of Recruitment showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:20 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:22 +msgid "Create a new job position from the main Recruitment dashboard by clicking the :guilabel:`New` button in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "Then, a :guilabel:`Create a Job Position` pop-up window will appear. From here, enter the name of the position (such as `Sales Manager`, `Mechanical Engineer`, etc.). When complete, click the :guilabel:`Create` button to save the entry, or the :guilabel:`Discard` button to delete it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Create a new job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment` dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:37 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:39 +msgid "After the job position is created, it's time to enter the details for the position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the relevant card to reveal several options, and then click :guilabel:`Configuration` to edit the details." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Edit the job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "Enter the job description in the :guilabel:`Job Summary` tab. This information is what is visible to potential applicants when searching for available jobs." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:53 +msgid "All the basic information about the job position is listed under the :guilabel:`Recruitment` tab. None of the fields are required, but it is a good idea to provide at least a few details, such as where the job is located." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:57 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:59 +msgid ":guilabel:`Department`: select the relevant department for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:60 +msgid ":guilabel:`Job Location`: select the physical address for the job." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid ":guilabel:`Employment Type`: select what type of position the job is, such as :guilabel:`Full-Time`, :guilabel:`Part-Time`, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid ":guilabel:`Company`: select the company the job is for." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:64 +msgid ":guilabel:`Target`: enter the number of employees to be hired for this position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid ":guilabel:`Is Published`: activate this option to publish the job online." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:66 +msgid ":guilabel:`Website`: select the website where the job will be published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:67 +msgid ":guilabel:`Recruiter`: select the person who will be doing the recruiting for this role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:68 +msgid ":guilabel:`Interviewers`: select who should perform the interview(s). Multiple people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid ":guilabel:`Interview Form`: select an :ref:`Interview form ` that applicants will fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:72 +msgid ":guilabel:`Contract Template`: select a contract template that will be used when offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:74 +msgid ":guilabel:`Process Details` section: this section contains information that is displayed online for the job position. This informs the applicants of the timeline and steps for the recruitment process, so they know when to expect a reply." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:78 +msgid ":guilabel:`Time to Answer`: enter the number of days before the applicant is contacted." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid ":guilabel:`Process`: enter the various stages the candidate will go through during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:81 +msgid ":guilabel:`Days to get an Offer`: enter the number of days before the applicant should expect an offer after the recruitment process has ended." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:85 +msgid "The :guilabel:`Process Details` section is a text field. All answers are typed in rather than selected from a drop-down menu. The text is displayed on the website exactly as it appears in this tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Enter job information details in the recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:96 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "An *Interview Form* is used to determine if a candidate is a good fit for a job position. Interview forms can be as specific or general as desired, and can take the form of a certification, an exam, or a general questionnaire. Interview forms are determined by the recruitment team." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:102 +msgid "All interview forms must be created, there are no pre-configured forms in Odoo. To create an interview form, start from the recruitment tab of the :guilabel:`Job Position` form. In the :guilabel:`Interview Form` field, enter a name for the new interview form. As the name is typed, several options populate beneath the entry, :guilabel:`Create (interview form name)`, :guilabel:`View all`, and :guilabel:`Create and edit...`. Click :guilabel:`Create and edit...`. and a :guilabel:`Create Interview Form` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "The option :guilabel:`View all` only appears if there are any interview forms already created. If no interview forms exist, the only options available are :guilabel:`Create (interview form name)`, and :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:114 +msgid "First, enter a name for the form in the :guilabel:`Name` field. This should be indicative of when the form should be used. For example, is the form specific to a job position, or is it a general form that can be used for all recruitment scenarios?" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:118 +msgid "Next, select what kind of interview form is being created. The default is :guilabel:`Custom`, which is pre-selected. The various options are :guilabel:`Survey`, :guilabel:`Live session`, :guilabel:`Assessment`, :guilabel:`Custom`, and :guilabel:`Appraisal`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:122 +msgid "Then select the person responsible for the form from the drop-down menu for the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:125 +msgid "If desired, an image can be added to the interview form. Mouse over the camera icon on the far right and a :guilabel:`✏️ (pencil)` icon appears. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:105 -msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date." +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The top portion of the new interview form with everything filled out and selected." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:109 -msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form." +#: ../../content/applications/hr/recruitment/new_job.rst:135 +#: ../../content/applications/hr/recruitment/new_job.rst:351 +msgid "Questions" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:112 -msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed." +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "In the :guilabel:`Questions` tab, click on :guilabel:`Add a section` to add a section to the form. A line appears, and a section heading can be entered. When complete, click off the line, or press enter to lock in the new section on the form." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:116 -msgid "Save and process new payslip" +#: ../../content/applications/hr/recruitment/new_job.rst:141 +msgid "Next, click :guilabel:`Add a question` to add a question to the section. A :guilabel:`Create Sections and Questions` pop-up window appears where the question details are entered. Type out the question in the top line." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:118 -msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/recruitment/new_job.rst:145 +msgid "There are several :guilabel:`Question Types` to choose from:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:122 -msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet." +#: ../../content/applications/hr/recruitment/new_job.rst:147 +msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question that only allows the candidate to select one answer" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:126 -msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." +#: ../../content/applications/hr/recruitment/new_job.rst:149 +msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question that allows the candidate to select multiple answers" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:132 -msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel Payslip` button." +#: ../../content/applications/hr/recruitment/new_job.rst:151 +msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:135 -msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." +#: ../../content/applications/hr/recruitment/new_job.rst:152 +msgid ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "The new payslip is emailed to the employee and the email appears in the chatter." +#: ../../content/applications/hr/recruitment/new_job.rst:153 +msgid ":guilabel:`Numerical Value`: only allows a number to be entered" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:143 -msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." +#: ../../content/applications/hr/recruitment/new_job.rst:154 +msgid ":guilabel:`Date`: a calendar module is presented to select a date" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click Make Payment to send the payment to the employee." +#: ../../content/applications/hr/recruitment/new_job.rst:155 +msgid ":guilabel:`Datetime`: a calendar module and a clock icon is presented to select a date and time" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:152 -msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form." +#: ../../content/applications/hr/recruitment/new_job.rst:156 +msgid ":guilabel:`Matrix`: a customizable table that allows the candidate to choose an answer for each row" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:156 -msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing." +#: ../../content/applications/hr/recruitment/new_job.rst:159 +msgid "After selecting a question type, a sample question appears in gray. This represents how the question will be displayed to applicants." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:0 -msgid "Banking information can be entered in an employee's card." +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Add a new question to the interview form." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:167 -msgid "All payslips" +#: ../../content/applications/hr/recruitment/new_job.rst:166 +msgid "Questions and sections can be reorganized. Move them by clicking and dragging individual section headings or question lines to their desired position(s)." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:169 -msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)." +#: ../../content/applications/hr/recruitment/new_job.rst:169 +msgid "Sections are indicated by a gray background, while questions have a white background." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:172 -msgid "Click on the :guilabel:`▶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`." +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "A sample of categories and questions for a candidate." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:179 -msgid ":guilabel:`Draft` indicates the payslip is created, and there is still time to make edits, since the amounts are not calculated." +#: ../../content/applications/hr/recruitment/new_job.rst:176 +#: ../../content/applications/hr/recruitment/new_job.rst:269 +msgid "Answers" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:181 -msgid "`Waiting` indicates the payslip has been calculated and the salary details can be found in the *Salary Computation* tab." +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "If :guilabel:`Multiple choice: only one answer`, :guilabel:`Multiple choice: multiple answers allowed`, :guilabel:`Single Line Text Box`, or :guilabel:`Matrix` is selected for the :guilabel:`Question Type`, an :guilabel:`Answers` tab appears beneath the question. If another question type is selected, the :guilabel:`Answers` tab remains hidden from view." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:183 -msgid "`Done` indicates the payslip is calculated and ready to be paid." +#: ../../content/applications/hr/recruitment/new_job.rst:185 +msgid "Multiple choice" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "View all payslips organized by batches. Click on the arrow to expand each batch." +#: ../../content/applications/hr/recruitment/new_job.rst:187 +msgid "For both the :guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed` question type, the answers are populated in the same way." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:189 -msgid "Click on an individual payslip to view the details for that payslip on a separate page. Using the breadcrumb menu, click :guilabel:`Employee Payslips` to go back to the list view of all payslips." +#: ../../content/applications/hr/recruitment/new_job.rst:190 +msgid "First, in the :guilabel:`Answers` tab, click :guilabel:`Add a line`. A line appears, and an answer can be entered. After typing in the answer, click off the line, or press enter to lock in the new answer on the form and have another answer line appear." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:192 -msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create a new payslip ` section." +#: ../../content/applications/hr/recruitment/new_job.rst:194 +msgid "If desired, an image can be attached to the answer. Click on a line to select it, and an :guilabel:`Upload your file` button appears on the right side. Click the :guilabel:`Upload your file` button and a file explorer window appears. Navigate to the image file, select it, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:197 -msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." +#: ../../content/applications/hr/recruitment/new_job.rst:199 +msgid "Repeat this for all the answers to be added for the multiple choice question. The answers can be rearranged in any order. To move an answer, click on the six small squares on the far left of each answer line, and drag the answer to the desired position. The order the answers appear in the form is the order the answers will appear online." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click on the Print smart button to print payslips to a PDF." +#: ../../content/applications/hr/recruitment/new_job.rst:204 +msgid "To delete a line, click on the :guilabel:`🗑️ (trash can)` icon on the far right side of the answer line." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:206 -msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet." +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "Answers to a multiple choice question, where each line has a different answer listed." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click on the Export All smart button to export all payslips to an Excel payslip." +#: ../../content/applications/hr/recruitment/new_job.rst:211 +msgid "Single Line Text Box" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:215 -msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." +#: ../../content/applications/hr/recruitment/new_job.rst:213 +msgid "If the :guilabel:`Single Line Text Box` question type is selected, only two checkboxes appear in the :guilabel:`Answers` tab:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:218 -msgid "Batches" +#: ../../content/applications/hr/recruitment/new_job.rst:216 +msgid ":guilabel:`Input must be an email`: activate this option if the answer must be in the format of an email address." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:220 -msgid "To view payslips in batches, navigate to :menuselection:`Payroll app --> Payslips --> Batches` to display all the payslip batches that have been created. These payslip batches are displayed in a list view, by default." +#: ../../content/applications/hr/recruitment/new_job.rst:219 +msgid ":guilabel:`Save as user email?`: this option appears if :guilabel:`Input must be an email` is selected. This saves the email entered on the form as the user's email, and will be used anytime Odoo contacts the user via email." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:224 -msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`." +#: ../../content/applications/hr/recruitment/new_job.rst:223 +msgid ":guilabel:`Save as user nickname?`: activate this option to populate the answer as the user's nickname. This is stored and used anywhere Odoo uses a nickname." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "View displaying all batches created." +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "The three possible checkboxes that can appear if a single line of text is selected\n" +"for the question type." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:231 -msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes." +#: ../../content/applications/hr/recruitment/new_job.rst:231 +msgid "Matrix" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:235 -msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data." +#: ../../content/applications/hr/recruitment/new_job.rst:233 +msgid "Sometimes, a question is asked that does not fit a standard answer format, and is best suited for a matrix. For example, asking an applicant what is their availability to work compared to the various shifts is a perfect question for a matrix format. In this example, an applicant can click on all the shifts they are available to work." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:238 -msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified." +#: ../../content/applications/hr/recruitment/new_job.rst:238 +msgid "For a :guilabel:`Matrix` question type, there are two sets of data that need to be input. The rows and columns must both be configured. The columns are represented by the :guilabel:`Choices` section, while the rows are configured in the :guilabel:`Rows` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:242 -msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus." +#: ../../content/applications/hr/recruitment/new_job.rst:242 +msgid "The method for populating both sections is the same. In the :guilabel:`Answers` tab, click :guilabel:`Add a line` in either the :guilabel:`Choices` or :guilabel:`Row` section. A line appears, and an answer can be entered. After typing in the answer, click off the line, or press enter to lock in the new answer on the form and have another answer line appear. Repeat this for all answers for both the :guilabel:`Choices` and :guilabel:`Rows` sections." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:247 -msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window." +#: ../../content/applications/hr/recruitment/new_job.rst:251 +msgid "This is an example matrix that asks an applicant what shifts they are available to work on Saturdays and Sundays, either morning, afternoon, or evening." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Generate payslips from the edited batch." +#: ../../content/applications/hr/recruitment/new_job.rst:255 +#: ../../content/applications/hr/recruitment/new_job.rst:440 +msgid "Description" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:256 -msgid "Back on the batch details page, click the :guilabel:`Create Draft Entry` smart button to create a draft of the payslips." +#: ../../content/applications/hr/recruitment/new_job.rst:257 +msgid "Enter any information that may be helpful to an applicant. This description will appear for this specific question only, and therefore should be question-specific and not generalized." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:263 -msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees." +#: ../../content/applications/hr/recruitment/new_job.rst:261 +#: ../../content/applications/hr/recruitment/new_job.rst:345 +msgid "Options" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:268 -msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner." +#: ../../content/applications/hr/recruitment/new_job.rst:263 +msgid "To view the options that are available to set for a question, click on the :guilabel:`Options` tab. The :guilabel:`Layout`, :guilabel:`Constraints`, and :guilabel:`Live Sessions` sections are universal for all :guilabel:`Question Types`, while the :guilabel:`Answers` tab is specific to the :guilabel:`Question Type` selected, and changes based on the selection." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:272 -msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." +#: ../../content/applications/hr/recruitment/new_job.rst:271 +msgid ":guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed`: a :guilabel:`Show Comments Field` option appears. Activate the option to allow the applicant to answer the question by typing in an answer (or comment). A :guilabel:`Comment Message` and :guilabel:`Comment is an answer` field appear if activated. Enter the text to appear in the :guilabel:`Comment Message` field. This should be helpful to the applicant, such as `If other, please specify`. Last, if the comment should be logged as the applicant's answer, activate the box." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click the Payslips smart button to view the individual payslips in the batch." +#: ../../content/applications/hr/recruitment/new_job.rst:278 +msgid ":guilabel:`Multiple Lines Text Box`: a :guilabel:`Placeholder` field appears. Enter any text that should appear with the question to help clarify how the applicant should answer." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:280 -msgid "Create a new batch" +#: ../../content/applications/hr/recruitment/new_job.rst:280 +msgid ":guilabel:`Single Line Text Box` and :guilabel:`Numerical Value`: a :guilabel:`Validate entry` option appears. Activate this option if what the applicant enters must be a numerical value, *and* needs to be verified. The answer can *only* be verified if it is a numerical entry. When activated, several other options appear. Enter the values for the :guilabel:`Min/Max Limits` in the two fields. Next, enter the text that appears when the answer given does not fit within the designated minimum and maximum parameters. Last, enter any text in the :guilabel:`Placeholder` field to provide any additional information or directions to assist the applicant." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:282 -msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page." +#: ../../content/applications/hr/recruitment/new_job.rst:287 +msgid ":guilabel:`Date` and :guilabel:`Datetime`: a :guilabel:`Validate entry` option appears. Activate this option if the applicant's answer needs to be verified. When activated, several other options appear. Enter the date ranges for the :guilabel:`Min/Max Limits` in the two fields. Click on a field, either the :guilabel:`minimum` or :guilabel:`maximum`, and a calendar appears. Select the dates for the corresponding fields. Next, enter the text that appears when the answer given does not fit within the designated minimum and maximum dates. Last, enter any text in the :guilabel:`Placeholder` field to provide any additional information or directions to assist the applicant." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:286 -msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`▼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates." +#: ../../content/applications/hr/recruitment/new_job.rst:295 +msgid ":guilabel:`Matrix`: the first option that appears is :guilabel:`Matrix Type`. Select either :guilabel:`One choice per row` or :guilabel:`Multiple choices per row` using the drop-down menu. The next option is :guilabel:`Show Comments Field`. Activate the option if there should be a comment displayed to the applicant. If activated, a :guilabel:`Comment Message` and :guilabel:`Comment is an answer` field appear. Enter the text to appear in the :guilabel:`Comment Message` field. This should be an instruction helpful to the applicant, such as `If other, please specify`. Last, if the comment should be logged as the applicant's answer, activate the box." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Enter the details for the new batch." +#: ../../content/applications/hr/recruitment/new_job.rst:304 +msgid "Constraints" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:295 -msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries." +#: ../../content/applications/hr/recruitment/new_job.rst:306 +msgid "If the question is required to be answered by the applicant, activate the box next to :guilabel:`Mandatory Answer`. An :guilabel:`Error message` field appears, with some example text in gray (*This question requires an answer*). Enter the message that should appear if the applicant attempts to move on to the next question without answering this required one. The text should explain that the question must be answered." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:299 -msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against." +#: ../../content/applications/hr/recruitment/new_job.rst:313 +msgid "Layout" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:301 -msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button." +#: ../../content/applications/hr/recruitment/new_job.rst:315 +msgid "If the question should only appear if a previous question is answered in a specific way, activate the :guilabel:`Conditional Display` option. A new :guilabel:`Triggering Question` field appears. Using the drop-down menu, select the previous question this new question is linked to. Once a previous question is selected, a :guilabel:`Triggering Answer` field appears. Select the answer that must be selected in order for the new question to appear." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:304 -msgid "To create the payslips for the newly-created batch, click the :guilabel:`Generate Payslips` button at the top of the form." +#: ../../content/applications/hr/recruitment/new_job.rst:322 +msgid "To further illustrate a triggering question, the following is an example that is applicable to recruitment. The question, `Do you have experience with managing a sales team?` is already added. A new question is then added, `How many years of experience?`. This question should *only* appear if the applicant selected `Yes` to the question `Do you have prior experience managing a sales team?`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:307 -msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`✖ (x mark)` icon at the far right of the payslip line." +#: ../../content/applications/hr/recruitment/new_job.rst:328 +msgid "To properly configure this example, activate the :guilabel:`Conditional Display` option. Then, select `Do you have experience with managing a sales team?` as the :guilabel:`Triggering Question`. Then, select :guilabel:`Yes` for the triggering answer." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:311 -msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus." +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "The layout field when properly configured for a conditional question." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:314 -msgid "Click the :guilabel:`Generate` button at the bottom of the pop-up window to create the payslips for the batch." +#: ../../content/applications/hr/recruitment/new_job.rst:338 +msgid "Live Sessions" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Generate payslips for the new batch." +#: ../../content/applications/hr/recruitment/new_job.rst:340 +msgid "If the question is for a live session, activate the :guilabel:`Question Time Limit` option. A :guilabel:`seconds` field appears. Enter the amount of time allotted for the applicant to enter the answer, in seconds." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:322 -msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters." +#: ../../content/applications/hr/recruitment/new_job.rst:347 +msgid "Next, configure the various options for the interview form. Click the :guilabel:`Options` tab to view all the options to configure, by category." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:326 -msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`✖ (x mark)` icon can be clicked to close the alert." +#: ../../content/applications/hr/recruitment/new_job.rst:353 +msgid ":guilabel:`Pagination`: choose how the questions should be displayed." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:330 -msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again." +#: ../../content/applications/hr/recruitment/new_job.rst:355 +msgid ":guilabel:`One page per question`: display a single question on each page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:333 -msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form." +#: ../../content/applications/hr/recruitment/new_job.rst:356 +msgid ":guilabel:`One page per section`: display each section with the corresponding questions on an individual page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:335 -msgid "From here, click the :guilabel:`Generate Draft Entry` button to change the payslips' status from :guilabel:`Draft` to :guilabel:`Done`." +#: ../../content/applications/hr/recruitment/new_job.rst:358 +msgid ":guilabel:`One page with all the questions`: display all sections and questions at the same time." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:338 -msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name." +#: ../../content/applications/hr/recruitment/new_job.rst:362 +msgid ":guilabel:`Display Progress as`: choose how to display the percentage of questions remaining to answer. This option only appears if either :guilabel:`One page per question` or :guilabel:`One page per section` is selected for :guilabel:`Pagination`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:343 -msgid "When done, click the :guilabel:`Confirm` button to confirm the information, or click :guilabel:`Cancel` to discard." +#: ../../content/applications/hr/recruitment/new_job.rst:366 +msgid ":guilabel:`Percentage left`: display the remaining amount in a percentage (%)." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:347 -msgid "Generate commission payslips" +#: ../../content/applications/hr/recruitment/new_job.rst:367 +msgid ":guilabel:`Number`: display the remaining amount in a numerical value." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:349 -msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button." +#: ../../content/applications/hr/recruitment/new_job.rst:370 +msgid ":guilabel:`Question Selection`: choose which questions are presented." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:354 -msgid "Doing so reveals a :guilabel:`Generate Commission Payslip` pop-up window, in which the necessary information **must** be filled out." +#: ../../content/applications/hr/recruitment/new_job.rst:372 +msgid ":guilabel:`All questions`: display the entire form, with all questions form all sections." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:373 +msgid ":guilabel:`Randomized per Section`: display only a random selection of questions from each section." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:377 +msgid ":guilabel:`Back Button`: activate this option if the applicant is able to click a back button to go back to previous questions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:381 +msgid "Although it is a selectable option, the :guilabel:`Randomized per section` option should only be used if receiving partial information/an incomplete survey from every applicant is acceptable to the business." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:386 +msgid "Time & Scoring" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:388 +msgid ":guilabel:`Survey Time Limit`: activate this option to limit the time allowed to complete the form. When selected, a field to enter the minutes appears next to the checked box. Enter the time (using an XX:XX minute/second format) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:391 +msgid ":guilabel:`Scoring`: choose how the questions should be scored." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:393 +msgid ":guilabel:`No scoring`: select this option to not score the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:394 +msgid ":guilabel:`Scoring with answers at the end`: select this option to score the form and display the correct answers for the candidate when they are finished with the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:396 +msgid ":guilabel:`Scoring without answers at the end`: select this option to score the form but not display the answers to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:399 +msgid ":guilabel:`Required Score (%)`: this option appears if one of the scoring options was selected. Enter the percentage the candidate needs to pass the exam (example, 80.00%). The entry should be written in an “XX.XX” format." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:403 +msgid ":guilabel:`Is a Certification`: activate this option if the form is a certification exam. When activated, a drop-down menu appears next to the checkbox. Select one of the default formats for the PDF certificate that will be sent to the candidate after completing the certification exam. Click the :guilabel:`Preview` button to view an example of the PDF certificate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:407 +msgid ":guilabel:`Certified Email Template`: if the :guilabel:`Is a Certification` box is activated, a :guilabel:`Certified Email Template` appears. Select the email template from the drop-down menu that is to be used when the applicant passes the test. Click the :guilabel:`External Link` icon to the right of the email template to preview the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:413 +msgid "Participants" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:415 +msgid ":guilabel:`Access Mode`: specify who can access the exam. Either :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:417 +msgid ":guilabel:`Require Login`: activate this option to require candidates to log in before taking the exam, whether they have a valid token or not." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:419 +msgid ":guilabel:`Limit Attempts`: if there is a limit to how many times the exam can be taken, activate this box, then enter the maximum attempt number in the field next to it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:423 +msgid "Live Session" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:425 +msgid ":guilabel:`Session Code`: enter the access code that will allow the viewers into the live exam session." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:427 +msgid ":guilabel:`Session Link`: the link appears in a box next to the :guilabel:`Session Link` option. Click the :guilabel:`Copy` button to copy the link." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:429 +msgid ":guilabel:`Reward quick answers`: if the exam is to be taken live, activate this option to award more points to participants who answer quickly." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:432 +msgid "After all fields have been entered, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Various options to configure for the interview form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:442 +msgid "When the applicant begins the survey, the text entered in this tab appears at the top of the survey page. Enter any information or descriptions that would be helpful to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:446 +msgid "End Message" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:448 +msgid "After the survey is complete, the message entered in this tab is displayed for the applicant." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:3 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Odoo's *Referrals* application is a centralized place where all information regarding referrals is housed, from points earned, coworkers hired, and rewards selected. Users can recommend people they know for job positions, then earn referral points as those people progress through the recruitment pipeline. Once enough referral points are earned, they can be exchanged for prizes. The Referrals application integrates with the *Employees*, *Recruitment*, and *Website* applications, all of which must be installed in order for the *Referrals* application to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:12 +msgid "The only configuration needed for the Referrals application after it is installed are the :ref:`rewards `; everything else is pre-configured when Odoo Referrals is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:16 +msgid "Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` rights for the Recruitment application has access to the Referrals application. Only user's with :guilabel:`Administrator` rights for the Recruitment application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users/manage_users` and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:24 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:26 +msgid "When opening the *Referrals* application for the first time, a pre-configured onboarding script appears. This is in the form of four slides, each explaining the different parts of the Referrals application. At the top of the dashboard, the following message is displayed throughout all the onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. Behind this main message is an image, and beneath it some more explanatory text." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:32 +msgid "Each of the onboarding slides has a corresponding image and message that is displayed. After reading each message, click the :guilabel:`Next` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:35 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:37 +msgid ":guilabel:`Oh no! Villains are lurking the city! Help us recruit a team of superheroes to save the day!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:40 +msgid ":guilabel:`Collect points and exchange them for awesome gifts in the shop.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "The onboarding slides will appear every time the Referrals application is opened, until all the slides have been viewed and the :guilabel:`Start Now` button has been clicked. If the onboarding is exited at any point, or if the :guilabel:`Start Now` button has *not* been clicked, the onboarding slides will begin again when the Referrals application is opened. Once the :guilabel:`Start Now` button has been clicked, the onboarding slides will not be seen again, and the main dashboard will load when the Referrals application is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:51 +msgid "At any point during onboarding, the :guilabel:`Skip` button may be clicked. This exits the onboarding, and the main Referrals dashboard loads. If :guilabel:`Skip` is clicked, onboarding slides will not load anymore when opening the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide with the skip and next buttons visible at the bottom." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:60 +msgid "If there are any candidates hired that the user had referred prior to opening the Referrals app (meaning the onboarding slides have not appeared before), when :guilabel:`Start Now` is clicked at the end of onboarding, instead of going to the main dashboard, a :ref:`hired ` screen appears instead." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:66 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:68 +msgid "Onboarding slides can be modified if desired. Only users with :guilabel:`Administrator` rights for the Recruitment application can modify onboarding slides. To edit a slide, navigate to :menuselection:`Referrals app --> Configuration --> Onboarding.` Each line displays the text for the individual onboarding slide. To edit an onboarding slide, click on an individual slide line to open the slide's onboarding form, then click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:74 +msgid "Make any changes to the message in the :guilabel:`Text` box. To change the order the slide appear in the onboarding, the :guilabel:`Sequence` can be modified. Type in the corresponding number to indicate the order in which the slides should be displayed. A :guilabel:`Company` may be selected, however, if this field is populated, that slide will only be displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:79 +msgid "The image can be modified as well. Hover over the image thumbnail in the top right corner of the form. A :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` icon to change the image. A file navigator window loads. Navigate to the desired image, select it, then click :guilabel:`Open`. The new image appears in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Enter the commission details." +#: ../../content/applications/hr/referrals.rst:86 +msgid "To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to delete any changes and revert to the original content." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:361 -msgid "On this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrows, navigate to the correct month, and click on the date to select it." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:366 -msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." +#: ../../content/applications/hr/referrals.rst:93 +msgid "The order of the slides can also be changed directly in the Onboarding dashboard, without having to edit an individual onboarding slide. Click the up and down arrow symbol that appears after the checkbox and before the slide text, and drag the slide to the desired position. The :guilabel:`Sequence` automatically changes on all the slide's onboarding forms, reflecting the new sequence." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:368 -msgid "When a department is selected, the employees listed for that department appear in the :guilabel:`Employee` section." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:371 -msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line." +#: ../../content/applications/hr/referrals.rst:104 +msgid "Share job positions" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:375 -msgid "Add a new entry by clicking :guilabel:`Add a Line`, and entering the :guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`." +#: ../../content/applications/hr/referrals.rst:106 +msgid "In order to earn referral points, a user must first share a job position so the applicant can apply for the position. There are several ways to share job positions within the Referrals application, through the :ref:`View Jobs ` button and the :ref:`Email A Friend ` button." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:378 -msgid "Click the :guilabel:`Upload Your File` button to add a file, if necessary. Any file type is accepted." +#: ../../content/applications/hr/referrals.rst:114 +msgid "View Jobs" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:381 -msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies." +#: ../../content/applications/hr/referrals.rst:116 +msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main Referrals dashboard. This presents all job positions, with each individual job presented in its own card." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:385 -msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The 'View Jobs' screen, displaying all current open job positions. All information is\n" +"displayed on the card." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:3 -msgid "Reporting" +#: ../../content/applications/hr/referrals.rst:125 +msgid "Each job position card contains the following information:" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:5 -msgid "The :guilabel:`Reporting` section of the *Payroll* app offers a variety of reports to choose from. The :guilabel:`Payroll`, :guilabel:`Meal Vouchers`, :guilabel:`Attachment of Salary`, and :guilabel:`DMFA` reports are universal and available for all companies regardless of location. The :guilabel:`Paid Time Off Allocation`, :guilabel:`273S Sheet`, and :guilabel:`274.XX Sheets` reports are specific to Belgian companies only." +#: ../../content/applications/hr/referrals.rst:127 +msgid "The title of the job position. This information is taken from the :guilabel:`Job Position` field of the job form." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:11 -msgid "To view a report, go to :menuselection:`Payroll --> Reporting` and click on the specific report." +#: ../../content/applications/hr/referrals.rst:129 +msgid "The number of positions being recruited. This information is taken from the :guilabel:`Expected New Employees` field of the :guilabel:`Recruitment` tab of the job form." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Report dashboard view." +#: ../../content/applications/hr/referrals.rst:131 +msgid "The points a user will earn when an applicant applies for the position." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:17 -msgid "If a report is unavailable to a company, a user error pops up, stating `You must be logged in to a Belgian company to use this feature.`" +#: ../../content/applications/hr/referrals.rst:132 +msgid "The job description detailing the job position. This information is taken from the :guilabel:`Job Position` tab of the job form." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:20 -msgid "At the top of each report, click on :guilabel:`Filters` to display the optional filters for the specific report. Filters show information that matches the specific filter parameters. For example, when selecting the :guilabel:`Last 365 Day Payslip` filter, only payslips for the last 365 days appear. All reports have the option to add a custom filter, and each have different default custom filter options. Select the parameters, then click the :guilabel:`Apply` button." +#: ../../content/applications/hr/referrals.rst:135 +msgid "To see all the details for a job position, click the :guilabel:`More Info` button on the specific card. This opens the job position webpage in a new browser tab. This is what an applicant sees before applying for a position." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:30 -msgid "Clicking on :guilabel:`Favorites` displays three options: :guilabel:`Save the current search`, :guilabel:`Add the search to the dashboard`, or :guilabel:`Insert the search to a Google spreadsheet`." +#: ../../content/applications/hr/referrals.rst:140 +msgid "Only published job positions will be visible in the Referrals app. To check which job positions are published or not, refer to the :doc:`recruitment/new_job` documentation." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Favorite options for reports." +#: ../../content/applications/hr/referrals.rst:144 +msgid "Refer friends" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:41 -msgid "Click on :menuselection:`Payroll --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report." +#: ../../content/applications/hr/referrals.rst:146 +msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` email pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:48 -msgid "This shows all the payslips generated in the last 365 days. The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various options to display. The options available include: :guilabel:`# Payslip`, :guilabel:`Basic Wage`, :guilabel:`Basic Wage for Time Off`, :guilabel:`Days of Paid Time Off`, :guilabel:`Days of Unforeseen Absence`, :guilabel:`Days of Unpaid Time Off`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, :guilabel:`Work Days`, :guilabel:`Work Hours`, and :guilabel:`Count`." +#: ../../content/applications/hr/referrals.rst:150 +msgid "The subject and body are populated using a default template. The subject `Job for you` appears, and can be modified if desired." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:61 -msgid "Line chart" +#: ../../content/applications/hr/referrals.rst:153 +msgid "The specific title of the job position will populate the :guilabel:`Job Position` placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website. When the prospective employee receives the email, the link will send them to the job position page, where they can apply for the position, and the person who referred them is tracked in the Referrals application." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:63 -msgid "A line chart is the default view for the *Payroll Analysis* report. If a different view was selected, click on the :guilabel:`Line Chart` icon (middle icon) in the menu bar to change the view back to a line chart. An option to display the line chart in ascending or descending order appears at the end of the options." +#: ../../content/applications/hr/referrals.rst:159 +msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Email` to send the email, or click :guilabel:`Cancel` to close the email pop-up window." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:73 -msgid "Bar chart" +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Referral email pop-up window with the email message inside it." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:75 -msgid "To display the data in a bar chart, click on the :guilabel:`Bar Chart` icon (first icon) in the menu bar." +#: ../../content/applications/hr/referrals.rst:168 +msgid "Share a job" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:82 -msgid "Click the :guilabel:`Stacked` icon to view the bar chart in a stacked format (where multiple values appear in each column). An option to display the columns in ascending or descending order appears at the end of the options." +#: ../../content/applications/hr/referrals.rst:170 +msgid "There are several other ways to share a job position aside from sending an email, via social media platforms and tracking links to the job position. At the bottom of each job position card are four icons and corresponding tracking links that can be used to share the job position, keeping track of applicants in the Referrals application." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:87 -msgid "Clicking an option enables it. To disable the option, click it again. When the option is enabled it appears grey. When it is inactive, it appears white." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The various sharing icons that appear for each job." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:91 -msgid "Pie chart" +#: ../../content/applications/hr/referrals.rst:180 +msgid "Link" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:93 -msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` icon (last icon) in the menu bar. There are no additional options available in this view." +#: ../../content/applications/hr/referrals.rst:182 +msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :guilabel:`🔗 (chain)` icon inside it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up. Next, share the link with the prospective employee however desired." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:101 -msgid "Pivot table" +#: ../../content/applications/hr/referrals.rst:189 +msgid "Facebook" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:103 -msgid "The bottom half of the :guilabel:`Payroll Analysis` dashboard presents a pivot table no matter which type of chart is selected for the top of the dashboard. The default information displayed is the number of payslips, net wage, gross wage, days of paid time off, and days of unpaid time off. The information is divided by department. To display more information on the report, select the :guilabel:`Measures` drop-down menu, then click on any other items to display." +#: ../../content/applications/hr/referrals.rst:191 +msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :guilabel:`f (Facebook icon)` inside it. If the user is already logged into Facebook, when the :guilabel:`f (Facebook icon)` is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to Facebook first." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:113 -msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, click on the column name twice. The first click selects the column, and the second click sorts the information in descending order." +#: ../../content/applications/hr/referrals.rst:197 +msgid "Type in any additional information to add to the post, in the space directly below your name. If desired, :guilabel:`tag` users, :guilabel:`check-in` at a location, or add a :guilabel:`status` to the post. To tag a user, click the :guilabel:`Tag Friends` icon and select the people to tag to the post. To add a check-in location, click the :guilabel:`Check in` icon, and select the location from the pop-up of predetermined locations based on your current location. To add a :guilabel:`status`, click the :guilabel:`Feeling/Activity` icon, then select either the feeling or the activity type, and lastly, if an activity type was selected, select the specific activity." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "To sort information by descending order, click the column head twice." +#: ../../content/applications/hr/referrals.rst:205 +msgid "There are five methods to share the job position, :guilabel:`Your Story`, :guilabel:`Share on a Friend's Timeline`, :guilabel:`Share in a Group`, :guilabel:`Share in an Event`, and :guilabel:`Share in a Private Message`. To select the sharing method, click the drop-down menu located at the top of the page, directly beneath the :guilabel:`Share on Facebook` banner." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:121 -#: ../../content/applications/hr/payroll/reporting.rst:172 -msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` icon. The information will be downloaded into an Excel spreadsheet." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The view on Facebook when sharing a job description. All the various ways to share are\n" +"highlighted, as are all the required settings." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Download an Excel spreadsheet of the data by clicking the download button." +#: ../../content/applications/hr/referrals.rst:217 +msgid "Share to news feed or story" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:128 -#: ../../content/applications/hr/payroll/reporting.rst:179 -msgid "The data can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A pop-up appears asking which spreadsheet to place the information in. Select an existing spreadsheet or enter the name for a new spreadsheet. Click the :guilabel:`Confirm` button to move to a spreadsheet view with all the information populated." +#: ../../content/applications/hr/referrals.rst:219 +msgid "The default sharing method is through the :guilabel:`News Feed`, :guilabel:`Story`, or both. At the lower portion of the form are radio buttons next to the two options, :guilabel:`Feed` (for the News Feed) and :guilabel:`Your Story` for stories. When :guilabel:`Share to News Feed or Story` is selected, these buttons are active, if another option is selected, these radio buttons are greyed out. Activate the radio button(s) to indicate how the job position should be shared, either in the news feed, the story, or both." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Send the data to a spreadsheet." +#: ../../content/applications/hr/referrals.rst:226 +msgid "The :guilabel:`Share to news feed or story` option allows for specific privacy settings to be selected. In the lower right corner of the screen, there are two drop-down menu options, one for the :guilabel:`Feed` option, the other for the :guilabel:`Your story` option. Select the posting parameters from the drop-down menus. The :guilabel:`Feed` ad :guilabel:`Your story` options appear different from user to user, depending on what privacy settings have been created in Facebook. :guilabel:`Public` and :guilabel:`Friends` are default options, but other options that the user may have configured will appear as well, such as custom groups." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:137 -msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the setting as a template to use in the future." +#: ../../content/applications/hr/referrals.rst:234 +msgid "When the post and/or story is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:141 -#: ../../content/applications/hr/payroll/reporting.rst:188 -msgid "The *Documents* application must be installed in order to use the :guilabel:`Insert in Spreadsheet` option." +#: ../../content/applications/hr/referrals.rst:237 +msgid "Share on a friend's timeline" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:146 -msgid "Meal Vouchers" +#: ../../content/applications/hr/referrals.rst:239 +msgid "Instead of making a public post on the user's on Facebook page, the job position can be shared directly on a friend's timeline. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share on a Fried's Timeline`." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:148 -msgid ":guilabel:`Meal Vouchers` provides an overview of the meal vouchers used by employees, and can be shown by :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`. The default view is by month." +#: ../../content/applications/hr/referrals.rst:243 +msgid "When selected, a :guilabel:`Friend` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. **Only** one friend can be selected." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Meal voucher" +#: ../../content/applications/hr/referrals.rst:247 +#: ../../content/applications/hr/referrals.rst:262 +#: ../../content/applications/hr/referrals.rst:276 +msgid "When the post is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:156 -msgid "To change the displayed view, click on :guilabel:`Total`. The data collapses, showing only the count column. Click on :guilabel:`Total` again, then hover over :guilabel:`Day`, then click on one of the other time-period options available." +#: ../../content/applications/hr/referrals.rst:250 +msgid "Share in a group" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:164 -msgid "It is possible to compare the current meal voucher report to the one for the previous time period or the previous year. To view these comparisons, click on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Date: Previous Period` or :guilabel:`Date: Previous Year`." +#: ../../content/applications/hr/referrals.rst:252 +msgid "To reach a specific audience and not share the job position publicly with everyone, a job can be shared in a group. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in a Group`." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:184 -msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the settings as a template to use in the future." +#: ../../content/applications/hr/referrals.rst:256 +msgid "When selected, a :guilabel:`Group` field appears below the selection. The available groups that can be posted to are groups the user is currently a member of. Job positions cannot be shared with groups the user has not joined. Begin to type in the name of the group. As the group name is typed, a list appears, populated with the group names that match what is entered. Select the group from the list. Only one group can be selected." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:192 -msgid "Attachment of Salary" +#: ../../content/applications/hr/referrals.rst:265 +msgid "Share in an event" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:194 -msgid "The :guilabel:`Attachment of Salary` report shows all deductions or allocations per employee, such as child support payments and wage garnishments." +#: ../../content/applications/hr/referrals.rst:267 +msgid "A job position can also be shared on an event page. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Event`." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "View the Attachment of Salary report that shows all salary garnishments." +#: ../../content/applications/hr/referrals.rst:270 +msgid "When selected, an :guilabel:`Event` field appears below the selection. The available events that can be posted to are events the user is invited to. This includes events that the user has not responded to yet, and events that have occurred in the past. Begin to type in the name of the event. As the event name is typed, a list appears, populated with the events that match what is entered. Select the event from the list. Only one event can be selected." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:201 -msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by month." +#: ../../content/applications/hr/referrals.rst:279 +msgid "Share in a private message" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:204 -msgid "The report can be exported as a XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top." +#: ../../content/applications/hr/referrals.rst:281 +msgid "The last option is to share a job position privately instead of publicly, in a Facebook message. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Private Message`." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:207 -msgid "Clicking on the :guilabel:`Measures` button shows options for how the data is displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count`, can all be selected or deselected by clicking on the item. If an item has a check mark, it is displayed." +#: ../../content/applications/hr/referrals.rst:285 +msgid "When selected, a :guilabel:`To` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. Multiple friends can be selected and added to a single message. Repeat this process for each friend to be added." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Select the options that be displayed in the report." +#: ../../content/applications/hr/referrals.rst:290 +msgid "When the message is ready to be sent, click the blue :guilabel:`Send message` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:216 -msgid "The salary attachment report can be compared to the one for the previous time period or the previous year. To view these comparisons, click on the on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`." +#: ../../content/applications/hr/referrals.rst:294 +msgid "X/Twitter" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:5 -msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." +#: ../../content/applications/hr/referrals.rst:296 +msgid "A job position can also be shared on X/Twitter. Click the :guilabel:`Share Now` button with the bird icon inside it. If the user is already signed in to X/Twitter, when the :guilabel:`Share Now` icon is clicked, an X/Twitter page loads in a new tab with a pre-populated message ready to post, in a draft pop-up. If the user is *not* already signed in, a sign-in screen loads instead, prompting the user to sign in to X/Twitter." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Work Entries dashboard view showing all employee's work entries." +#: ../../content/applications/hr/referrals.rst:302 +msgid "The default message is:" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:13 -msgid "To change the view so that only the entries for a single day, week, or month are shown, click on one of the corresponding links for :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`, located at the top of the dashboard." +#: ../../content/applications/hr/referrals.rst:304 +msgid ":guilabel:`Amazing job offer for (Job Position)! Check it live: (link to Job Position)`" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:17 -msgid "Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons on the left and right side of the :guilabel:`Today` button to adjust the displayed dates. The arrows will adjust the date based on the type of time selected. For example, if month is selected, the arrows will move one month with each click of the arrow. If week or day is selected, the time will move by either a week or a day for each click of the arrow, respectively." +#: ../../content/applications/hr/referrals.rst:306 +msgid "Type in any additional information or make any edits to the message. If desired, click the :guilabel:`X` in the top left corner of the thumbnail preview of the webpage to remove it. To adjust the audience for the message, click the drop-down button labeled :guilabel:`Everyone`. Select the preferred audience from the drop-down menu. The default option is :guilabel:`Everyone`, and the other options is :guilabel:`Circle`. The :guilabel:`Circle` is a group of people that the user has selected in X/Twitter." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:24 -msgid "Adding a new work entry" +#: ../../content/applications/hr/referrals.rst:313 +msgid "The default setting is :guilabel:`🌎 (globe) Everyone can reply`, an allows everyone on X/Twitter to reply to the message. To change this, click the :guilabel:`🌎 (globe) Everyone can reply` button in the lower left section of the message. There are four options presented: :guilabel:`Everyone`, :guilabel:`Accounts you follow`, :guilabel:`Verified accounts`, and :guilabel:`Only accounts you mention`. Selecting one of the other options restricts who can reply to the message." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:26 -msgid "If a work entry is missing and needs to be added, such as sick time or time off, click :guilabel:`Add` to create a new work entry. A pop-up will appear, with several fields to fill in." +#: ../../content/applications/hr/referrals.rst:319 +msgid "There are various other items that can be added to the message. Media (photos, videos, etc), GIF's, polls, emojis, and a location may all be added. Click the corresponding icon in the bottom left of the message and follow the prompts to add the desired additional elements." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:29 -msgid "Enter the :guilabel:`Work Entry Name`, such as `Sick Time` or any other short description. Select the :guilabel:`Employee` and the :guilabel:`Work Entry Type` from the respective drop-down lists." +#: ../../content/applications/hr/referrals.rst:323 +msgid "To have the message posted at a future date and time, click the :guilabel:`Schedule` icon in the lower left of the message window. It is the fifth icon from the left. Enter the date and time that the message should be posted using the date and time selector presented. Click :guilabel:`Confirm` to add the scheduled time to the message." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Filling in the work entry Create form in Odoo." +#: ../../content/applications/hr/referrals.rst:328 +msgid "To post the message, click :guilabel:`Post`. The message will be immediately posted, or, if it was scheduled, will be posted at the scheduled date and time." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:36 -msgid "Next, enter the date and time for the work entry in the :guilabel:`From` and :guilabel:`To` drop-downs. First, select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The X/Twitter pop-up when sharing a job description. All the other items than can be added\n" +"to the message are highlighted, as is the visibility setting and the post button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:40 -msgid "Then, select the time by clicking on the :guilabel:`⏰ (clock)` icon, and using the :guilabel:`⬆️ (up arrow)` and :guilabel:`⬇️ (down arrow)` icons for each section to enter the hour, minute, and second for the time period." +#: ../../content/applications/hr/referrals.rst:337 +msgid "LinkedIn" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:44 -msgid "The :guilabel:`Period` will display the hours based on the :guilabel:`To` and :guilabel:`From` entries." +#: ../../content/applications/hr/referrals.rst:339 +msgid "To share a job position on LinkedIn, click the :guilabel:`Share Now` button with the :guilabel:`in (LinkedIn logo)` inside it. If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:48 -msgid "Before clicking either :guilabel:`Save & Close` or :guilabel:`Save & New`, it is good to double check the :guilabel:`Period` to ensure the time stated corresponds to the :guilabel:`To` and :guilabel:`From` fields." +#: ../../content/applications/hr/referrals.rst:345 +msgid "The job position can be shared either in a public post, or in a private message to an individual or group of individuals." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:0 -msgid "Hours entered in the Period field." +#: ../../content/applications/hr/referrals.rst:349 +msgid "Share in a post" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:56 -msgid "Once the information is entered, click :guilabel:`Save & Close` to save the entry and close the pop-up, or :guilabel:`Save & New` to save the entry and create another :guilabel:`Work Entry Type`." +#: ../../content/applications/hr/referrals.rst:351 +msgid "To share the job position in a public post, click the :guilabel:`✏️ (pencil) Share in a post` button in the lower-left corner of the screen. A :guilabel:`Create a post` window loads, with the job position link populated. Enter any other information to the post in the field." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:60 -msgid "Regenerate work entries" +#: ../../content/applications/hr/referrals.rst:355 +msgid "To change the audience that will see the post, click the :guilabel:`🌎 (globe) Anyone` drop-down, located directly beneath the account name. Click on the desired selection, then click the :guilabel:`Save` button on the far right side of the screen, beneath the last listed option." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:62 -msgid "After a work entry has been either added or modified, the work entries need to be regenerated for the affected employee(s). Click on the :guilabel:`Regenerate Work Entries` button at the top of the main dashboard, and a pop-up will appear." +#: ../../content/applications/hr/referrals.rst:359 +msgid ":guilabel:`Anyone` allows anyone on LinkedIn to see the post. :guilabel:`Connections only` will only share the post with people who are connected with the user, and will be hidden from everyone else. :guilabel:`Group` shares the post with a specific group the user is a member of. The post can only be shared with one group; posting to multiple groups at once is not available. If :guilabel:`Group` is selected, a page loads with a list of all the groups the user is currently a member of. Click on a group to select it, then click the :guilabel:`Save` button in the lower right corner." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:66 -msgid "Select the :guilabel:`Employee` to regenerate work entries for from the :guilabel:`drop-down menu`, and adjust the :guilabel:`From` and :guilabel:`To` fields so the correct date range is displayed. Click the :guilabel:`Regenerate Work Entries` button and the work entries will be recreated. Once finished, the pop-up will close." +#: ../../content/applications/hr/referrals.rst:367 +msgid "Next, select who can comment on the post. To change this setting, click on the :guilabel:`💬 (speech bubble) Anyone` button located beneath the body of the post. A page loads with the various options. Click on one of the three options to select it. The three options are :guilabel:`Anyone`, :guilabel:`Connections only`, and :guilabel:`No one`. The default option is :guilabel:`Anyone`, which allows anyone with a LinkedIn account to comment on the post. :guilabel:`Connections only` will only allow people who are connected with the user to comment on the post. :guilabel:`No one` turns off commenting. After making a selection, click the :guilabel:`Save` button in the far lower right corner." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Regenerate a work entry for a particular employee." +#: ../../content/applications/hr/referrals.rst:376 +msgid "Finally, once the post is edited and the settings have been selected, click :guilabel:`Post` to share the job position." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:76 -msgid "Conflicts" +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A linkedIn post to share a job. The job position is highlighted as is the post button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:78 -msgid "A conflict appears for any request that has not been approved, such as sick time or vacation, or if there are any errors on the work entry, such as required fields being left blank. Conflicts are required to be resolved before payslips can be generated." +#: ../../content/applications/hr/referrals.rst:384 +msgid "Send as private message" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:82 -msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` overview dashboard, located by going to :menuselection:`Payroll --> Work Entries --> Conflicts`, where only conflicts needing resolution are shown." +#: ../../content/applications/hr/referrals.rst:386 +msgid "Instead of making a public post, the post can be sent to a connection in a private message. To do so, click the :guilabel:`Send as private message` button in the lower left corner. A message window loads with the link to the job description in the bottom of the window. First, select the recipient(s) for the message. Type the name in the :guilabel:`Search for message recipients` field. As the name is typed in, any matching connections appear. Click on a connection to add them. Repeat this for all the recipients to send the message to. There is no limit on the number of connections that can be messaged. Next, enter any additional text in the message body. Click :guilabel:`Send` in the lower right corner to send the message. A :guilabel:`Message successfully sent!` screen loads. Two options are presented, :guilabel:`View Message` and :guilabel:`Continue to LinkedIn`. Click on the desired selection to navigate to that choice, or close the browser tab to exit." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Conflicts dashboard view showing all employee's conflicts in work entries." +#: ../../content/applications/hr/referrals.rst:400 +msgid "Email a friend" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:90 -msgid "Conflicts are indicated with an orange triangle in the top left corner of each individual entry. Click on an individual work entry to see the conflict details in a pop-up." +#: ../../content/applications/hr/referrals.rst:402 +msgid "Another way to share job opportunities is to share the entire current list of open job positions instead of one job position at a time. To do this, navigate to the main *Referrals* app dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:93 -msgid "The conflict is briefly explained in an orange text box." +#: ../../content/applications/hr/referrals.rst:407 +msgid "Enter the email address(es) in the :guilabel:`Email` line. The email can be sent to multiple recipients, simply enter a comma followed by a single space after each email address. The :guilabel:`Subject` is pre-configured with `Job for you`, but can be edited." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Details for a conflict appear in the pop-up." +#: ../../content/applications/hr/referrals.rst:411 +msgid "The email body is also populated with pre-configured text. The text that appears is:" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:99 -msgid "The :guilabel:`Work Entry Name`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up. The :guilabel:`From` and :guilabel:`To` date range, as well as the total time requested (in hours), appear in the :guilabel:`Period` field on the right side." +#: ../../content/applications/hr/referrals.rst:413 +msgid "`Hello,`" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:103 -msgid "If there is a conflict because a time-off request for the same time already exists in the system, the time-off will be entered in the :guilabel:`Time Off` field. Clicking the :guilabel:`External Link` button next to the :guilabel:`Time Off` entry will bring up the duplicate time-off request." +#: ../../content/applications/hr/referrals.rst:415 +msgid "`There are some amazing job offers in my company! Have a look, they can be interesting for you`" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:107 -msgid "The details for the time-off request appear in the pop-up. The request can be modified if needed. Click either the :guilabel:`Validate` or :guilabel:`Refuse` button to approve or deny the request, then click the :guilabel:`Save` button to save the changes." +#: ../../content/applications/hr/referrals.rst:417 +msgid "`See Job Offers`" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Edit and/or validate a duplicate time-off request." +#: ../../content/applications/hr/referrals.rst:419 +msgid "The `See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for, that are live on the company's website (published). Add any additional text and/or make any edits to the message body, then click :guilabel:`Send Mail` to send the email. The message will be sent and the window will close." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:115 -msgid "Once the duplicate time-off request has been approved and saved, the screen goes back to the conflict. Click :guilabel:`Refuse Time Off` or :guilabel:`Approve Time Off` via the buttons in the top right to either approve or deny the request. Repeat for all conflicts until there are no conflicts to resolve." +#: ../../content/applications/hr/referrals.rst:427 +msgid "Hired referrals" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:120 -msgid "After conflicts have been resolved, work entries must be regenerated for each employee by clicking the :guilabel:`Regenerate Work Entries` button, and entering the corresponding information for each employee." +#: ../../content/applications/hr/referrals.rst:429 +msgid "When a candidate that has been referred by a user is hired, the user \"grows their superhero team\" and adds superhero avatars to their Referrals dashboard." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Regenerate Work Entries button on the Work Entries Regeneration form." +#: ../../content/applications/hr/referrals.rst:432 +msgid "After a referral has been hired, when the user next opens the Referrals app, instead of the main dashboard, a hired page loads. The text :guilabel:`(Referral Name) has been hired! Choose an avatar for your new friend!` appears." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:129 -msgid "Generating payslips" +#: ../../content/applications/hr/referrals.rst:436 +msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is greyed out, and the name the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:131 -msgid "To generate payslips, navigate to the time period the payslips should be generated for, either day, week, or month. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button." +#: ../../content/applications/hr/referrals.rst:440 +msgid "If more than one referral was hired since opening the Referrals application, after selecting the first avatar, the user is prompted to select another avatar for the subsequent hired referral. Once all avatars have been selected, the dashboard loads and all the avatars are now visible. Mouse over each avatar and their name is displayed above them." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Generate Payslips button on the Work Entry dashboard." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The hired screen. A selection of avatars are presented to chose from, with any already\n" +"chosen are greyed out." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:140 -msgid "If the :guilabel:`Generate Payslips` button is not active (appears light turquoise instead of dark turquoise), that indicates there are conflicts. *Solve conflicts first* will appear as a warning when :guilabel:`Generate Payslips` is moused over. Resolve all conflicts before generating payslips." +#: ../../content/applications/hr/referrals.rst:451 +msgid "Modify friends" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:145 -msgid "A batch entry will appear for the time period selected. The batch name appears at the top in the :guilabel:`Name` field, typically listing the month and year for the particular batch." +#: ../../content/applications/hr/referrals.rst:453 +msgid "Friend avatars are able to be modified in the same manner that :ref:`levels ` are modified. Only users with :guilabel:`Administrator` rights for the Recruitment application can make modifications to friends. The pre-configured friends can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Friends`. Each friend avatar appears in the :guilabel:`Dashboard Image` column, and the corresponding name appears in the :guilabel:`Friend Name` column. The default images are a motley group of hero characters, ranging from robots to dogs." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:148 -msgid "The date range the payslips apply to appears in the :guilabel:`Period` field. The company appears in the :guilabel:`Company` field, along with an option to mark the payslips as a credit note. To make changes, click the :guilabel:`Edit` button in the top left, make any changes, then click either :guilabel:`Save` to accept the changes or :guilabel:`Discard` to revert to the original data." +#: ../../content/applications/hr/referrals.rst:460 +msgid "To modify a friend's dashboard image, thumbnail, name, or position, click on an individual friend to open the referral friend form. Click :guilabel:`Edit` to make modifications. Type the name in the :guilabel:`Friend Name` field. The name is solely to differentiate the friends in the configuration menu; the friend's name is not visible anywhere else in the Referrals application." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Batch information that appears when making a batch." +#: ../../content/applications/hr/referrals.rst:465 +msgid "The :guilabel:`Position` can be set to either :guilabel:`Front` or :guilabel:`Back`. This determines the position of the friend in relation to the user's super hero avatar. Click the radio button next to the desired selection, and the friend will appear either in front of or behind the user's avatar when activated." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:157 -msgid "Click the :guilabel:`Create Draft Entry` button to create the payslips for the batch." +#: ../../content/applications/hr/referrals.rst:470 +msgid "If desired, both the thumbnail :guilabel:`Image` and the :guilabel:`Dashboard Image` can be modified. Hover over the image being replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:159 -msgid "Click on the :guilabel:`Payslips` button in the top right to view all the payslips for the batch." +#: ../../content/applications/hr/referrals.rst:475 +#: ../../content/applications/hr/referrals.rst:660 +msgid "Once all changes have been made, click the :guilabel:`Save` button to save the changes, or click the :guilabel:`Discard` button to revert to the original information." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:162 -msgid "Payslips will have a status of *Waiting* until the :guilabel:`Create Draft Entry` button has been clicked. After, the payslip status will change to *Done*." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:165 -msgid "Payslips can be printed by clicking the box next to each payslip to print, or clicking the box next to :guilabel:`Reference` to select all the payslips at once. Click the :guilabel:`Print` button, and a PDF file will be created with all the specified payslips." +#: ../../content/applications/hr/referrals.rst:483 +#: ../../content/applications/hr/referrals.rst:668 +msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the Referrals application." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:-1 -msgid "Print button for printing the payslips." +#: ../../content/applications/hr/referrals.rst:487 +msgid "Once an image is changed and the friend is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:174 -msgid ":ref:`Configure work entries `" +#: ../../content/applications/hr/referrals.rst:492 +msgid "Referral points" msgstr "" -#: ../../content/applications/hr/recruitment.rst:5 -#: ../../content/applications/hr/recruitment/new_job.rst:60 -msgid "Recruitment" +#: ../../content/applications/hr/referrals.rst:494 +msgid "The referral program is based on earning points that are then exchanged for rewards. On the main Referrals application dashboard, the top displays a summary of the user's current points. The left side of the summary displays the total points earned, and the right side displays the points that are available to spend." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:3 -msgid "Job positions" +#: ../../content/applications/hr/referrals.rst:499 +msgid "To see the various referrals and the points earned for each, click on one of the buttons directly beneath the avatars. The options are :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:5 -msgid "In the default :menuselection:`Recruitment` dashboard view, all job positions are shown, regardless of status. Current published positions with active applicants are shown, as well as job positions that have been created but have not yet been published." +#: ../../content/applications/hr/referrals.rst:503 +msgid "The current number of referrals who are still active in the recruitment pipeline, and have not yet been hired or refused, appear above the :guilabel:`Ongoing` button. The number of referrals who have been hired appear above the :guilabel:`Successful` button. The total number of referrals (both the ongoing and successful referrals combined) appear above the :guilabel:`Referrals` button." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:9 -msgid "Each job position is shown in an individual kanban card. If the job position is active and candidates can apply, then a :guilabel:`Published` banner will appear in the top-right corner of the card." +#: ../../content/applications/hr/referrals.rst:509 +msgid "To view the referrals associated with each of the categories, :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`, click on the corresponding button. All the referrals for that specific category are displayed." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:13 -msgid "View submitted applications by clicking the :guilabel:`# Applications` button, with `#` being the number of applications received. If a position is not published, a :guilabel:`Start Recruitment` button will appear instead." +#: ../../content/applications/hr/referrals.rst:514 +msgid "My referrals" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Main dashboard view of Recruitment showing all job positions." +#: ../../content/applications/hr/referrals.rst:516 +msgid "To see all the referrals (both ongoing and successful) click the :guilabel:`Referrals` button. A :guilabel:`My Referral` window loads. This screen displays all the referrals, with each referral in its own referral card." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:22 -msgid "Create a new job position" +#: ../../content/applications/hr/referrals.rst:520 +msgid "A successful referral has a green line down the left side of the card, and displays a :guilabel:`✓ Hired` image in the top right corner of the card. Referrals that are in process display an :guilabel:`In Progress` image in the top right corner." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:24 -msgid "There are two ways a job position can be created: from the main :guilabel:`Recruitment` dashboard, or from the :guilabel:`Configuration` menu." +#: ../../content/applications/hr/referrals.rst:524 +msgid "Each referral card lists the name of the applicant, the department the job position is in, the name of the job position, the person responsible for filling the role (recruiter), and the points earned." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:27 -msgid "To create a job position from the :guilabel:`Configuration` menu, go to :menuselection:`Recruitment app --> Configuration --> Job Positions`. The job positions in this view are displayed in a list." +#: ../../content/applications/hr/referrals.rst:528 +msgid "Points" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:30 -msgid "Create a new job position from the :guilabel:`Job Positions` dashboard by clicking the :guilabel:`Create` button in the top-left corner." +#: ../../content/applications/hr/referrals.rst:530 +msgid "The points that can be earned for a referral are the same across all job positions. Each stage of the recruitment process has corresponding points assigned to it. The stages listed correspond to the stages configured in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:33 -msgid "Then, a :guilabel:`Create a Job Position` pop-up window will appear. From here, enter the name of the position (such as `Sales Manager`, `Mechanical Engineer`, etc.). When complete, click the :guilabel:`Create` button to save the entry, or the :guilabel:`Discard` button to delete it." +#: ../../content/applications/hr/referrals.rst:534 +msgid "On each individual referral card, beneath the points earned is a bar chart that displays how many points have been earned out of the total possible points that can be earned if the applicant is hired." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Create a new job position." +#: ../../content/applications/hr/referrals.rst:538 +msgid "Beneath the bar chart is a list of the various recruitment stages and the points earned when the referral moves to that stage. If a stage has been achieved and the points have been earned, a green check mark appears next to the stage." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:41 -msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment`` dashboard, as well as in the list view on the :guilabel:`Configuration` dashboard." +#: ../../content/applications/hr/referrals.rst:543 +msgid "The pre-configured point structure for referrals is as follows:" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:46 -msgid "Edit a new job position" +#: ../../content/applications/hr/referrals.rst:545 +msgid ":guilabel:`Initial Qualification`: 1 point" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:48 -msgid "Once the job position is created, it's time to enter the details for the position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the relevant card to reveal several options, and then click :guilabel:`Edit` to edit the details." +#: ../../content/applications/hr/referrals.rst:546 +msgid ":guilabel:`First Interview`: 20 points" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Edit the job position card." +#: ../../content/applications/hr/referrals.rst:547 +msgid ":guilabel:`Second Interview`: 9 points" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:56 -msgid "Enter the job description in the :guilabel:`Job Description` tab. This information is what is visible to potential employees when searching for available jobs." +#: ../../content/applications/hr/referrals.rst:548 +msgid ":guilabel:`Contract Proposal`: 5 points" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:62 -msgid "All the basic information about the job position is listed under the :guilabel:`Recruitment` tab. None of the fields are required, but it is a good idea to provide at least a few details, such as where the job is located." +#: ../../content/applications/hr/referrals.rst:549 +msgid ":guilabel:`Contract Signed`: 50 points" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:66 -msgid "The fields can be filled out as follows:" +#: ../../content/applications/hr/referrals.rst:551 +msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage is done in the Recruitment application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:68 -msgid ":guilabel:`Company`: Select the company the job is for." +#: ../../content/applications/hr/referrals.rst:558 +msgid "Rewards" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:69 -msgid ":guilabel:`Website`: Select the website where the job will be published." +#: ../../content/applications/hr/referrals.rst:561 +msgid "Create rewards" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:70 -msgid ":guilabel:`Department`: Select the relevant department for the job position." +#: ../../content/applications/hr/referrals.rst:563 +msgid "The rewards are the only configurations needed when setting up the Referrals application. Only users with :guilabel:`Administrator` rights for the Recruitment application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`Create` and a reward form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:71 -msgid ":guilabel:`Expected New Employees`: Enter the number of employees to be hired for this position." +#: ../../content/applications/hr/referrals.rst:568 +msgid ":guilabel:`Product Name`: Enter the name as it should appear for the reward." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:72 -msgid ":guilabel:`Contract Template`: Select a contract template that will be used when offering the job to a candidate." +#: ../../content/applications/hr/referrals.rst:569 +msgid ":guilabel:`Cost`: Enter the amount of points required to redeem the reward." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:74 -msgid ":guilabel:`Interview Form`: Select a form that applicants will fill out prior to their interview, or create a new form. Once selected, a :guilabel:`Display (Name) Form` button will appear next to the selected form. Click on this to see how the form will be displayed to the candidate on the front end." +#: ../../content/applications/hr/referrals.rst:570 +msgid ":guilabel:`Company`: Using the drop-down menu, select the company the reward will appear for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:0 -msgid "The interview form will display a link to see the form as the candidate will." +#: ../../content/applications/hr/referrals.rst:573 +msgid ":guilabel:`Gift Responsible`: Select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is purchased, so they know when to deliver the reward to the recipient." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:83 -msgid ":guilabel:`Recruiter`: Select the person who will be doing the recruiting for this role." +#: ../../content/applications/hr/referrals.rst:576 +msgid ":guilabel:`Description`: Type in the description for the reward. This will be visible on the reward card, beneath the title." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Enter job information details in the recruitment tab." +#: ../../content/applications/hr/referrals.rst:578 +msgid ":guilabel:`Photo`: Add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:90 -msgid "Appraisals" +#: ../../content/applications/hr/referrals.rst:583 +msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company`, and :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:92 -msgid "This tab displays the :guilabel:`Employee Feedback Template` and the :guilabel:`Manager Feedback Template`, both of which will be used after the employee has been hired, the predetermined time has passed, and feedback is requested." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A filled out reward form with all details entered." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:97 -msgid "Create interview form" +#: ../../content/applications/hr/referrals.rst:591 +msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost will be listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon will be displayed on the rewards page." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:99 -msgid "Once a job position has been made, the :guilabel:`Interview Form` needs to be created. In the kanban view of the :menuselection:`Recruitment` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the card to reveal several options, and then click :guilabel:`Create Interview Form`." +#: ../../content/applications/hr/referrals.rst:596 +msgid "Redeem rewards" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Create an interview form for the new position." +#: ../../content/applications/hr/referrals.rst:598 +msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:108 -msgid "Click on :guilabel:`Add a section` to add a section to the form. A line will appear, and a section heading can be entered. When complete, click off the line, or press enter to lock in the new section on the form." +#: ../../content/applications/hr/referrals.rst:605 +msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A confirmation pop-up appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:116 -msgid "Next, click :guilabel:`Add a question` to add a question to the section. A pop-up window appears to enter the question details. Type out the question in the top line." +#: ../../content/applications/hr/referrals.rst:609 +msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:119 -msgid "There are several *Question Types* to choose from:" +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Buy button appears below a mug and backpack reward, while the bicycle reward states how\n" +"many more reward points are needed to redeem." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:121 -msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" +#: ../../content/applications/hr/referrals.rst:621 +msgid "Levels" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:122 -msgid ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" +#: ../../content/applications/hr/referrals.rst:623 +msgid "The referrals application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:123 -msgid ":guilabel:`Numerical Value`: only allows a number to be entered" +#: ../../content/applications/hr/referrals.rst:627 +msgid "Levels have no functional impact on the performance of the application. They are solely used for the purpose of adding achievement tiers for participants to aim for, gamifying referrals for the user." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:124 -msgid ":guilabel:`Date`: a calendar module is presented to select a date" +#: ../../content/applications/hr/referrals.rst:630 +msgid "The user's current level is displayed at the top of the main Referrals application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:125 -msgid ":guilabel:`Datetime`: a calendar module and a clock icon is presented to select a date and time" +#: ../../content/applications/hr/referrals.rst:637 +msgid "Modify levels" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:126 -msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question that only allows the candidate to select one answer" +#: ../../content/applications/hr/referrals.rst:639 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:128 -msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question that allows the candidate to select multiple answers" +#: ../../content/applications/hr/referrals.rst:646 +msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form. Click :guilabel:`Edit` to make modifications." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:130 -msgid ":guilabel:`Matrix`: a customizable table that allows the candidate to choose an answer for each row" +#: ../../content/applications/hr/referrals.rst:649 +msgid "Type in the name or number of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Add a new question to the interview form." +#: ../../content/applications/hr/referrals.rst:655 +msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:137 -msgid "Questions and sections can be reorganized. Move them by clicking and dragging individual section headings or question lines to their desired position(s)." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:140 -msgid "Sections are indicated by a gray background, while questions have a white background." +#: ../../content/applications/hr/referrals.rst:672 +msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "A sample of categories and questions for a candidate." +#: ../../content/applications/hr/referrals.rst:677 +msgid "Level up" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:146 -msgid "Next, configure the options for the interview form. Click the :guilabel:`Options` tab to view all the options to configure, by category." +#: ../../content/applications/hr/referrals.rst:679 +msgid "Once enough points have been accumulated to level up, the circle around the user's photo is completely filled in with a cyan color, a large image stating :guilabel:`Level up!` appears above the photo, and the phrase :guilabel:`Click to level up!` appears beneath the user's photo and current level." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:150 -msgid "Questions" +#: ../../content/applications/hr/referrals.rst:684 +msgid "Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the text :guilabel:`Click to level up!` beneath the user's photo to level up the user. The user's avatar changes to the current level, and the ring around the photo is updated to indicate the current amount of points." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:152 -msgid ":guilabel:`Layout`: Choose how the questions should be displayed." +#: ../../content/applications/hr/referrals.rst:688 +msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:154 -msgid ":guilabel:`One page with all the questions`: Display all sections and questions at the same time." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Level up!' appears\n" +"above their image." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:156 -msgid ":guilabel:`One page per section`: Display each section with the corresponding questions on an individual page." +#: ../../content/applications/hr/referrals.rst:697 +msgid "Once a user has reached the highest configured level, they will continue to accrue points that can be redeemed for rewards, but they are no longer able to level up. The ring around their photo remains solid cyan." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:158 -msgid ":guilabel:`One page per question`: Display a single question on each page." +#: ../../content/applications/hr/referrals.rst:702 +msgid "Alerts" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:160 -msgid ":guilabel:`Progression Mode`: Display the progress the candidate is making, either as a :guilabel:`Percentage`, or as a :guilabel:`Number`." +#: ../../content/applications/hr/referrals.rst:704 +msgid "In the Referrals application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:162 -msgid ":guilabel:`Survey Time Limit`: Check this box to limit the time allowed to complete the form. When selected, a field to enter the minutes appears next to the checked box. Enter the time (using an XX:XX minute/second format) in the field." +#: ../../content/applications/hr/referrals.rst:709 +msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the Referrals application for the first time in a new session." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:165 -msgid ":guilabel:`Selection`: Display the entire form (e.g. :guilabel:`All questions`), or only a random selection of questions from each section (:guilabel:`Randomized per section`)." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Two alert banners appear above the user's photo." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:169 -msgid "Although it is a selectable option, the :guilabel:`Randomized per section` option is not typically selected for an interview form." +#: ../../content/applications/hr/referrals.rst:719 +msgid "Create an alert" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:173 -msgid "Scoring" +#: ../../content/applications/hr/referrals.rst:721 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:175 -msgid ":guilabel:`No scoring`: Select this option to not score the form." +#: ../../content/applications/hr/referrals.rst:725 +msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:176 -msgid ":guilabel:`Scoring with answers at the end`: Select this option to score the form and display the" +#: ../../content/applications/hr/referrals.rst:727 +msgid ":guilabel:`Date From`: The date the alert starts. On this date, the alert will be visible on the dashboard." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:177 -msgid "correct answers for the candidate when they are finished with the form." +#: ../../content/applications/hr/referrals.rst:729 +msgid ":guilabel:`Date To`: The date the alert ends. After this date, the alert will be hidden from view." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:178 -msgid ":guilabel:`Scoring without answers at the end`: Select this option to score the form but not display the answers to the candidate." +#: ../../content/applications/hr/referrals.rst:730 +msgid ":guilabel:`Company`: The current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the Referrals application. If a company is specified, only user's within that company (who also have access to the Referrals application) will see the alert." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:181 -msgid "If one of the scoring options was selected, a :guilabel:`Success %` field will appear. Enter the percentage the candidate needs to pass the exam (example, 80.00%). The entry should be written in an “XX.XX” format." +#: ../../content/applications/hr/referrals.rst:735 +msgid ":guilabel:`Alert`: Enter the text for the alert. This message appears inside the alert banner on the main dashboard." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:186 -msgid "Candidates" +#: ../../content/applications/hr/referrals.rst:737 +msgid ":guilabel:`On Click`: There are three options for the alert. Click the radio button next to the desired selection. The options are:" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:188 -msgid ":guilabel:`Access Mode`: Specify who can access the exam. Either :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +#: ../../content/applications/hr/referrals.rst:740 +msgid ":guilabel:`Not Clickable`: The alert only displays text, there is no link to click." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:190 -msgid ":guilabel:`Appraisal Managers Only`: Check this box so only the managers who are reviewing the exam can see the answers. If left unchecked, anyone can view the results." +#: ../../content/applications/hr/referrals.rst:741 +msgid ":guilabel:`Go to All Jobs`: The alert contains a link that when clicked, navigates to the website with all the currently posted job positions." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:192 -msgid ":guilabel:`Login Required`: Check this box to require candidates to log in before taking the exam, whether they have a valid token or not." +#: ../../content/applications/hr/referrals.rst:743 +msgid ":guilabel:`Specify URL`: The alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:194 -msgid ":guilabel:`Attempts Limit`: If there is a limit to how many times the exam can be taken, check this box, then enter the maximum attempt number in the field next to it." +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An alert form completely filled in with all selections entered." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:198 -msgid "Live Session" +#: ../../content/applications/hr/referrals.rst:756 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application have access to the Reporting feature in Referrals. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:200 -msgid ":guilabel:`Reward quick answers`: If the exam is to be taken live, check this box to award more points to participants who answer quickly." +#: ../../content/applications/hr/referrals.rst:760 +msgid "In the top portion of the window, the report displays a bar chart of how many referred candidates are hired, and how many are still in the hiring pipeline. The candidates are further divided by channel, showing specifically where the referral came from, such as a direct referral, Facebook, etc. If a channel does not appear on the report, that indicates there are no referrals from that particular channel." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:202 -msgid ":guilabel:`Session Code`: Enter an access code that will allow the viewers into the live exam session." +#: ../../content/applications/hr/referrals.rst:766 +msgid "The middle third provides all the specific data that has been tracked. This includes how many total points have been earned across all referrals, how many applicants were referred, hired, or refused, how many applicants the current logged-in user referred, how many total points were earned, and how many points were given for refused applicants." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:205 -msgid "After all fields have been entered, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the changes." +#: ../../content/applications/hr/referrals.rst:771 +msgid "The bottom third displays a pivot table. This table can be inserted into a new or existing spreadsheet. To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up appears, asking which spreadsheet to insert the pivot chart into. Select the desired spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click :guilabel:`Confirm` and the selected spreadsheet loads, with the new table in it." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Various options to configure for the interview form." +#: ../../content/applications/hr/referrals.rst:778 +msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed in order to use the :guilabel:`Insert in Spreadsheet` option." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 6f55b7bd28..f75fa2c5aa 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -38,35 +38,179 @@ msgid "Daily operations" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:3 -msgid "Process to an Inventory Adjustment with Barcodes" +msgid "Apply inventory adjustments with barcodes" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:5 -msgid "To process an inventory adjustment by using barcodes, you first need to open the *Barcode* app. Then, from the application, click on *Inventory Adjustments*." +msgid "In a warehouse, the recorded inventory counts in the database might not always match the actual, real inventory counts. In such cases, inventory adjustments can be made to reconcile the differences, and ensure that the recorded counts in the database match the actual counts in the warehouse. In Odoo, the *Barcode* app can be used to make these adjustments." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:13 -msgid "If you want to fully work with barcodes, you can download the sheet *Commands for Inventory*." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:10 +msgid "These adjustments can be done in real time using an Odoo-compatible barcode scanner or the Odoo mobile app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:16 -msgid "Once you have clicked on *Inventory Adjustments*, Odoo will automatically create one. Note that, if you work with multi-location, you first need to specify in which location the inventory adjustment takes place." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:14 +msgid "For a list of Odoo-compatible barcode mobile scanners, and other hardware for the *Inventory* and *Barcode* apps, refer to the `Odoo Inventory • Hardware page `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:19 +msgid ":doc:`../../inventory/warehouses_storage/inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:22 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:15 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:13 +msgid "Enable Barcode app" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:24 -msgid "If you don’t work with multi-location, you will be able to scan the different products you want to include in the inventory adjustment." +msgid "To use the *Barcode* app to create and apply inventory adjustments, it **must** be installed by enabling the feature from the settings of the *Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:27 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click the checkbox next to the :guilabel:`Barcode Scanner` option." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:31 -msgid "If you have 5 identical articles, scan it 5 times or use the keyboard to set the quantity." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:24 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:22 +msgid "Once the checkbox is ticked, click :guilabel:`Save` at the top of the page to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:33 +msgid "After saving, a new drop-down menu appears under the :guilabel:`Barcode Scanner` option, labeled :guilabel:`Barcode Nomenclature`, where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. Each nomenclature option determines how scanners interpret barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:38 +msgid "There is also a :guilabel:`Configure Product Barcodes` internal link arrow, along with a set of :guilabel:`Print` buttons for printing barcode commands and a barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Enabled Barcode feature in Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:46 +msgid "For more information on setting up and configuring the :guilabel:`Barcode` app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and :doc:`Activate the Barcodes in Odoo <../setup/software>` docs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:51 +msgid "Perform an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:53 +msgid "Begin by navigating to the :menuselection:`Barcode app --> Barcode Scanning` dashboard, where different options will be displayed, including :guilabel:`Operations`, :guilabel:`Inventory Adjustments`, and :guilabel:`Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:57 +msgid "To create and apply inventory adjustments, click on the :guilabel:`Inventory Adjustments` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:60 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:123 +msgid "Doing so navigates to the *Barcode Inventory Client Action* page, labeled as :guilabel:`Inventory Adjustment` in the top header section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Barcode app start screen with scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:67 +msgid "To begin the adjustment, first scan the *source location*, which is the current location in the warehouse of the product whose count should be adjusted. Then, scan the product barcode(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:70 +msgid "The barcode of a specific product can be scanned multiple times to increase the quantity of that product in the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:74 +msgid "If the warehouse *multi-location* feature is **not** enabled in the database, a source location does not need to be scanned. Instead, simply scan the product barcode to start the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:78 +msgid "Alternatively, the quantity can be changed by clicking the :guilabel:`✏️ (pencil)` icon on the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:81 +msgid "Doing so opens a separate window with a keypad. Edit the number in the :guilabel:`Quantity` line to change the quantity. Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the number keys can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:86 +msgid "In the below inventory adjustment, the source location `WH/Stock/Shelf/2` was scanned, assigning the location. Then, the barcode for the product `[FURN_7888] Desk Stand with Screen` was scanned 3 times, increasing the units in the adjustment. Additional products can be added to this adjustment by scanning the barcodes for those specific products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Barcode Inventory Client Action page with inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:95 +msgid "To complete the inventory adjustment, click the green :guilabel:`✅ Apply` button with the check mark at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:98 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:150 +msgid "Once applied, Odoo navigates back to the :guilabel:`Barcode Scanning` screen. A small green banner appears in the top right corner, confirming validation of the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:180 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:103 +msgid "Odoo's *Barcode* application provides demo data with barcodes to explore the features of the app. These can be used for testing purposes, and can be printed from the home screen of the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:106 +msgid "To access this demo data, navigate to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes sheet` and :guilabel:`commands for Inventory` (bolded and highlighted in blue) in the information pop-up window above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Demo data prompt pop-up on Barcode app main screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:115 +msgid "Manually add products to inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:117 +msgid "When the barcodes for the location or product are not available, Odoo *Barcode* can still be used to perform inventory adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:120 +msgid "To do this, navigate to the :menuselection:`Barcode app --> Barcode Scanning --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:126 +msgid "To manually add products to this adjustment, click the white :guilabel:`➕ Add Product` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:129 +msgid "This navigates to a new, blank page where the desired product, quantity, and source location must be chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Keypad to add products on Barcode Inventory Client Action page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:136 +msgid "First, click the :guilabel:`Product` line, and choose the product whose stock count should be adjusted. Then, manually enter the quantity of that product, either by changing the `1` in the :guilabel:`Quantity` line, or by clicking the :guilabel:`+1` and :guilabel:`-1` buttons to add or subtract quantity of the product. The number pad can be used to add quantity, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:34 -msgid "Besides using the barcode scanner, you can also manually add a product if necessary. To do so, click on *Add Product* and fill the information in manually." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:141 +msgid "Below the number pad is the :guilabel:`location` line, which should read `WH/Stock` by default. Click this line to reveal a drop-down menu of locations to choose from, and choose the :guilabel:`source location` for this inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:44 -msgid "When you have scanned all the items of the location, validate the inventory manually or scan the *Validate* barcode." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:145 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:147 +msgid "To apply the inventory adjustment, click the green :guilabel:`✅ Apply` button with the check mark, at the bottom of the page." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 @@ -770,6 +914,9 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:41 msgid "10" msgstr "" @@ -799,6 +946,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:42 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 @@ -1025,96 +1173,394 @@ msgstr "" msgid "Reception stock move record for 52.1 kg of peaches." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:3 -msgid "Process to Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:3 +msgid "Process receipts and deliveries with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:7 +msgid "The *Barcode* app can be used to process receipts, deliveries, and other types of operations in real time using a barcode scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:10 +msgid "This makes it possible to process operations on the warehouse floor when they happen, instead of having to wait to validate transfers from a computer. Processing operations this way can help to properly attribute barcodes to the appropriate products, pickings, locations, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:17 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:15 +msgid "To use the *Barcode* app to process transfers, it must be installed by enabling the feature from the settings of the *Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:20 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:18 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click the checkbox next to the :guilabel:`Barcode Scanner` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:26 +msgid "Once the page has refreshed, new options will be displayed under the :guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with a corresponding drop-down menu), where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:30 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:29 +msgid "There is also a :guilabel:`Configure Product Barcodes` internal link arrow, and a set of :guilabel:`Print` buttons for printing barcode commands and a barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:37 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:36 +msgid "For more on setting up and configuring the :guilabel:`Barcode` app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and :doc:`Activate the Barcodes in Odoo <../setup/software>` documentation pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:44 +msgid "Scan barcodes for receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:46 +msgid "To process warehouse receipts for incoming products, there first needs to be a purchase order (PO) created, and a receipt operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:49 +msgid "To create a :abbr:`PO (purchase order)`, navigate to the :menuselection:`Purchase app --> Create` to create a new request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:52 +msgid "From the blank :abbr:`RFQ (request for quotation)` form, click the drop-down menu next to the :guilabel:`Vendor` field to add a vendor. Then, on the :guilabel:`Product` line under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:57 +msgid "Once ready, click :guilabel:`Save` at the top of the form, then click :guilabel:`Confirm Order` to confirm the :abbr:`RFQ (request for quotation)` to a :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Completed purchase order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:64 +msgid "To process and scan barcodes for warehouse receipts, navigate to the :menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:66 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented. To process receipts, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :menuselection:`Operations` overview page." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:8 -msgid "Simple Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:74 +msgid "From this page, locate the :guilabel:`Receipts` card, and click the :guilabel:`# To Process` button to view all outstanding receipts. Then, select the desired receipt operation to process. This navigates to the barcode transfer screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:10 -msgid "To process a transfer from the *Barcode* app, the first step is to go to *Operations*." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:79 +msgid "If *only* using a barcode scanner or the Odoo mobile app, the barcodes for each transfer of a corresponding operation type can be scanned to be processed easily. Once scanned, the products that are part of an existing transfer can be scanned, and new products can be added to the transfer, as well. Once all products have been scanned, validate the transfer to proceed with the stock moves." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:16 -msgid "Then, you have the choice to either enter an existing transfer, by going to the corresponding operation type and manually selecting the one you want to enter, or by scanning the barcode of the transfer." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:85 +msgid "From this screen, an overview of all receipts to process within that transfer (**WH/IN/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:26 -msgid "From there, you will be able to scan the products that are part of the existing transfer and/or add new products to this transfer. Once all the products have been scanned, you can validate the transfer to proceed with the stock moves." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Overview of receipts in transfer to scan." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:35 -msgid "If you have different storage locations in your warehouse, you can add additional steps for the different operation types." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:94 +msgid "To process and scan each product individually, choose a specific product line. The :guilabel:`+#` button (in this case, :guilabel:`+10`) can be clicked to indicate receipt of that product, or the :guilabel:`pencil` icon can be clicked to open a new screen to edit that product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:41 -msgid "Receipts" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:98 +msgid "From this screen, the product that's being received is listed. Under the product name, the :guilabel:`Quantity` line can be edited. Either change the `0` in the line to the desired quantity, or click the :guilabel:`/# Units` button (in this case, :guilabel:`/10 Units`) to automatically fill the quantity ordered from the :abbr:`PO (purchase order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:43 -msgid "When receiving a product in stock, you need to scan its barcode in order to identify it in the system. Once done, you can either make it enter the main location of the transfer, for example WH/Stock, or scan a location barcode to make it enter a sub-location of the main location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:104 +msgid "In the reception operation `WH/IN/00019`, `10 Units` of the `Barcode Product` is expected to be received. `[BARCODE_PROD]` is the :guilabel:`Internal Reference` set on the product form. Scan the barcode of the `Barcode Product` to receive one unit. Afterwards, click the :guilabel:`pencil` icon to manually enter the received quantities." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:52 -msgid "If you want the product to enter WH/Stock in our example, you can simply scan the next product." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Product line editor for individual transfer in Barcode app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:56 -msgid "Delivery Orders" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:113 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:179 +msgid "Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the :guilabel:`number keys` can be used to add quantity, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:58 -msgid "When delivering a product, you have to scan the source location if it is different than the one initially set on the transfer. Then, you can start scanning the products that are delivered from this specific location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:116 +msgid "Below the :guilabel:`number keys` is the :guilabel:`location` line, which reads `WH/Stock` by default, unless another *location* is listed on the product itself. Click this line to reveal a drop-down menu of additional locations to choose from." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:66 -msgid "Once the different products have been scanned, you have the possibility to scan another location, such as WH/Stock, and another page will be added to your delivery order. You can move from one to the other thanks to the *Previous* and *Next* buttons." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:120 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:158 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:211 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes made to the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:74 -msgid "Now, you can validate your transfer. To do so, click on *Next* until you reach the last page of the transfer. There, you will be able to validate it." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:122 +msgid "Then, from the overview page with all receipts to process within that transfer (**WH/IN/000XX**), click the :guilabel:`+#` button on the product line for the products being received, and click :guilabel:`Validate`. The receipt has now been processed, and the :guilabel:`Barcode app` can be closed out." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:82 -msgid "Internal Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Overview of receipts in transfer to validate." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:84 -msgid "When realizing an internal transfer with multi-location, you first have to scan the source location of the product. Then, you can scan the product in itself, before having to scan the barcode of the destination location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:132 +msgid "Scan barcodes for delivery orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:89 -msgid "If the source and destination of the internal transfers are already correct, you don’t need to scan them." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:134 +msgid "To process warehouse deliveries for outgoing products, there first needs to be a sales order (SO) created, and a delivery operation to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:93 -msgid "Transfers with Tracked Products" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:137 +msgid "To create a :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales app --> Create` to create a new quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:95 -msgid "If you work with products tracked by lot/serial numbers, you have two ways of working:" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:140 +msgid "From the blank quotation form, click the drop-down menu next to the :guilabel:`Customer` field to add a customer. Then, on the :guilabel:`Product` line under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:98 -msgid "If you work with serial/lot numbers taking all products into consideration, you can scan the barcode of the lot/serial number and Odoo will increase the quantity of the product, setting its lot/serial number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:144 +msgid "Once ready, click :guilabel:`Save` at the top of the form, and click :guilabel:`Confirm Order` to confirm the quotation to a :abbr:`SO (sales order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:103 -msgid "If you have the same lot/serial number for different products, you can work by scanning the product barcode first, and then the barcode of the lot/serial number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Completed sales order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:151 +msgid "To process and scan barcodes for warehouse deliveries, navigate to the :menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:153 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented. To process deliveries, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :guilabel:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:157 +msgid "From this page, locate the :guilabel:`Delivery Orders` card, and click the :guilabel:`# To Process` button to view all outstanding deliveries. Then, select the desired delivery order to process. This navigates to the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Operations overview page in Barcode app dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:165 +msgid "From this screen, an overview of all deliveries to process within that transfer (**WH/OUT/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:170 +msgid "To process and scan each product individually, choose a specific product line. The :guilabel:`+1` button can be clicked to indicate delivery of that product, or the :guilabel:`pencil icon` can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:174 +msgid "From this screen, the product that's being delivered is listed. Under the product name, the :guilabel:`Quantity` line can be edited. Either change the `0` in the line to the desired quantity, or click the :guilabel:`/# Units` button (in this case, :guilabel:`/10 Units`) to automatically fill the quantity ordered from the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:182 +msgid "Below the :guilabel:`number keys` is the :guilabel:`location` line, which reads `WH/Stock` by default, unless another location is listed on the product itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:185 +msgid "This is the location that the product is being pulled from for delivery. Click this line to reveal a drop-down menu of additional locations to choose from (if this product is stored in multiple locations in the warehouse)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:190 +msgid "For warehouses that have multiple different storage locations, putaway rules, and removal strategies, additional steps can be added for various operation types, while using the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:196 +msgid "Then, from the overview page with all receipts to process within that transfer (**WH/OUT/000XX**), click the :guilabel:`+#` button on the product line for the products being received, and click :guilabel:`Validate`. The delivery has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Overview of deliveries in transfer to validate." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:3 -msgid "Create a Transfer from Scratch" +msgid "Create and process transfers with barcodes" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:5 -msgid "To create a transfer from the *Barcode* application, you first need to print the operation type barcodes. To do so, you can download the *Stock barcode sheet* from the home page of the app." +msgid "The *Barcode* app can be used to process internal transfers for all types of products, including transfers for products tracked using lots or serial numbers. Transfers can be created from scratch in real time using an Odoo-compatible barcode scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:9 +msgid "For a list of Odoo-compatible barcode mobile scanners, and other hardware for the *Inventory* app, refer to the `Odoo Inventory • Hardware page `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:24 +msgid "When the page has refreshed, new options are displayed under the :guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with a corresponding drop-down menu), where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. The nomenclature selected changes how scanners interpret barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:41 +msgid "Scan barcodes for internal transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:43 +msgid "To create and process internal transfers for products in a warehouse, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features **must** be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:12 -msgid "Once done, you can scan the one for which you want to create a new document. Then, an empty document will be created and you will be able to scan your products to populate it." +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:46 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:50 +msgid "Then, click :guilabel:`Save` at the top of the page to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:53 +msgid "Create an internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:55 +msgid "To process existing internal transfers, there first needs to be an internal transfer created, and an operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:58 +msgid "To create an internal transfer, navigate to the :menuselection:`Inventory app`. From the :guilabel:`Inventory Overview` dashboard, locate the :guilabel:`Internal Transfers` card, and click on the :guilabel:`0 To Process` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:62 +msgid "Then, click :guilabel:`Create` in the top left of the resulting page. This navigates to a new :guilabel:`Internal Transfer` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:65 +msgid "On this blank form, the :guilabel:`Operation Type` is automatically listed as :guilabel:`Internal Transfers`. Under that field, the :guilabel:`Source Location` and :guilabel:`Destination Location` are set as :guilabel:`WH/Stock` by default, but can be changed to whichever locations the products are being moved from, and moved to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Blank internal transfer form with source location and destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:74 +msgid "Once the desired locations have been selected, products can be added to the transfer. On the :guilabel:`Product` line under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:78 +msgid "Once ready, click :guilabel:`Save` at the top of the form to save the new internal transfer. Once saved, click the :guilabel:`Detailed Operations` icon (four lines, at the far right of the :guilabel:`Product` line) to open the :guilabel:`Detailed Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Internal transfer detailed operations pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:86 +msgid "From the pop-up, click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:88 +msgid "Then, in the :guilabel:`To` column, change the location from :guilabel:`WH/Stock` to a different location, where the products should be moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:91 +msgid "Next, in the :guilabel:`Done` column, change the quantity to the desired quantity to transfer. Once ready, click :guilabel:`Confirm` to close out the pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:95 +msgid "Scan barcodes for internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:97 +msgid "To process and scan barcodes for internal transfers, navigate to the :menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:99 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:102 +msgid "To process internal transfers, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :menuselection:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:109 +msgid "From this page, locate the :guilabel:`Internal Transfers` card, and click the :guilabel:`# To Process` button to view all outstanding internal transfers. Then, select the desired operation to process. This navigates to the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:114 +msgid "When using the *Barcode* app without the *Inventory* app (**only** if using a barcode scanner or the Odoo mobile app), the barcodes for each transfer of a corresponding operation type can be scanned to be processed easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:118 +msgid "Once scanned, the products that are part of an existing transfer can be scanned, and new products can be added to the transfer, as well. Once all products have been scanned, validate the transfer to proceed with the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:122 +msgid "From this screen, an overview of all products to process within that specific internal transfer (**WH/INT/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:131 +msgid "Then, scan the barcode of the product to process the internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:133 +msgid "Or, to process and scan each product individually, choose a specific product line. The :guilabel:`+ 1` button can be clicked to add additional quantity of that product to the transfer, or the :guilabel:`pencil icon` can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:137 +msgid "In the product's pop-up window, the product and the units to process is displayed with a number pad. Under the product name, the :guilabel:`Quantity` line can be edited. Change the number in the line to the quantity listed to be transferred on the internal transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:142 +msgid "In the internal transfer operation `WH/INT/000XX`, `50 Units` of the `Transfer Product` is moved from `WH/Stock` to `WH/Stock/Shelf 1`. `[TRANSFER_PROD]` is the :guilabel:`Internal Reference` set on the product form. Scan the barcode of the `Transfer Product` to receive one unit. Afterwards, click the :guilabel:`pencil icon` to manually enter the transferred quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:151 +msgid "Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the number keys can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:154 +msgid "Below the number keys are the two :guilabel:`location` lines, which read whichever locations were previously specified on the internal transfer form, in this case `WH/Stock` and `WH/Stock/Shelf 1`. Click these lines to reveal a drop-down menu of additional locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:160 +msgid "Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The receipt has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:165 +msgid "The *Barcode* app can also be used to scan products in internal transfers containing unique lot numbers and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:168 +msgid "From the barcode transfer screen, scan the barcode of a lot or serial number, and Odoo automatically increases the quantity of the product to the quantity recorded in the database. If the same lot or serial number is shared between different products, scan the product barcode first, then the barcode of the lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:174 +msgid "Create a transfer from scratch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:176 +msgid "In addition to processing and scanning barcodes for existing, previously-created internal transfers, the *Barcode* app can also be used to create transfers from scratch, simply by scanning a printed operation type barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:182 +msgid "Odoo's *Barcode* application provides demo data with barcodes to explore the features of the app. These can be used for testing purposes, and can be printed from the home screen of the app. To access this demo data, navigate to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes sheet` (bolded and highlighted in blue) in the information pop-up above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:191 +msgid "To do this, first navigate to the :menuselection:`Barcode app`. Once inside the *Barcode* app, a :guilabel:`Barcode Scanning` screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:194 +msgid "From this screen, when using a USB or bluetooth barcode scanner, directly scan the product barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:196 +msgid "When using a smartphone as the barcode scanner, click the :guilabel:`Tap to Scan` button (next to the camera icon, at the center of the screen). This opens a :guilabel:`Barcode Scanner` pop-up screen that enables the camera of the device being used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:200 +msgid "Face the camera toward the printed operation type barcode to scan it. Doing so processes the barcode, and navigates to a barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:203 +msgid "From this screen, an overview of all products to process within that specific internal transfer (**WH/INT/000XX**) is shown. Since this is a new transfer created from scratch, however, there should not be any products listed on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:207 +msgid "To add products, scan the product barcode. If the barcode is not available, manually enter the product into the system by clicking the :guilabel:`Add Product` button at the bottom of the screen, and add the products and product quantities that should be transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Blank product editor in scratch internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:217 +msgid "Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The internal transfer has now been processed, and the *Barcode* app can be closed out." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup.rst:5 @@ -2019,55 +2465,112 @@ msgid "Product tracking" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 -msgid "What's the difference between lots and serial numbers?" +msgid "Difference between lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:5 +msgid "*Lots* and *serial numbers* are the two ways to identify and track products in Odoo. While there are similarities between the two traceability methods, there are also notable differences that affect receipts, deliveries, and inventory reports." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:6 -msgid "Introduction" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:9 +msgid "A *lot* usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse. However, it can also pertain to a batch of products manufactured in-house, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:8 -msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:13 +msgid "A *serial number* is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items or products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:12 -msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:17 +msgid ":doc:`lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:15 -msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:20 -msgid "When to use" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:23 +msgid "To track products using lots and serial numbers, the *Lots & Serial Numbers* feature must be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:22 -msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:26 +msgid "To do that, go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:28 -msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled lots and serial numbers feature in inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:34 -msgid "When not to use" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:35 +msgid "When to use lots" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:36 -msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:37 +msgid "Lots are useful for products that are manufactured or received in large quantities, such as clothes or food. Lots and can be used to trace a product back to a group, which is especially useful when managing product recalls or expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:40 -msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "Created lot with quantity of products in it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 -msgid ":doc:`serial_numbers`" +msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their life cycles." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:47 -msgid ":doc:`lots`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:52 +msgid "When to use serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:54 +msgid "The goal of assigning serial numbers to individual products is to make sure every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services related to products they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "List of serial numbers for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:63 +msgid "Serial numbers can contain many different types of characters: numbers, letters, typographical symbols, or a mixture of all three types." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 +msgid "Traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 +msgid "Manufacturers and companies can refer to traceability reports to see the entire life cycle of a product. These reports include vital information, like where it came from (and when), where it was stored, and to whom it was sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:73 +msgid "To see the full traceability of a product, or group products by lots and/or serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:77 +msgid "From here, products with lots or serial numbers assigned to them are listed by default. They can also be expanded to show what lots or serial numbers have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:80 +msgid "To group by lots or serial numbers, first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:85 +msgid "Doing so reveals all existing lots and serial numbers, and each can be expanded to show all product quantities with that assigned number. For unique serial numbers that are *not* reused, there should *only* be one product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 +msgid "Reporting page with drop-down lists of lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:94 +msgid "For additional information regarding an individual lot number or serial number, click the line item for the lot or serial number to reveal that specific number's :guilabel:`Lot` or :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number. Any operations made using that lot or serial number can be found here, as well." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 @@ -2386,23 +2889,10 @@ msgstr "" msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 -msgid "Enable lots & serial numbers" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 -msgid "Enabled lots and serial numbers feature in inventory settings." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 msgid "Track products by lots" msgstr "" @@ -2472,31 +2962,31 @@ msgstr "" msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 msgid "Manage lots on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 msgid "Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:108 msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:111 msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:115 msgid "Choose the desired quantity of the product to order by changing the number in the :guilabel:`Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:118 msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:124 msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned." msgstr "" @@ -2504,19 +2994,19 @@ msgstr "" msgid "Add lot/serial number user error popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:133 msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:137 msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 msgid "There are two ways to assign lot numbers: **manually** and **copy/paste**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:142 msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." msgstr "" @@ -2524,11 +3014,11 @@ msgstr "" msgid "Assign lot number detailed operations popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:151 msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:155 msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." msgstr "" @@ -2536,67 +3026,67 @@ msgstr "" msgid "List of lot numbers copied on excel spreadsheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:165 msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:168 msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 msgid "Manage lots on delivery orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 msgid "Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:178 msgid "To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so reveals a new, blank quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:181 msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:221 msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:187 msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:194 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:132 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:230 msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:198 msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:200 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:202 msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:205 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:207 msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:215 msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." msgstr "" @@ -2604,35 +3094,35 @@ msgstr "" msgid "Detailed operations popup for source lot number on sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:223 msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:226 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:228 msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:230 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 msgid "Manage lots for different operations types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:234 msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:235 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:237 msgid "For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order, only existing lot numbers can be used." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:238 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:240 msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:242 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:244 msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:247 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:249 msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes." msgstr "" @@ -2640,31 +3130,31 @@ msgstr "" msgid "Enabled traceability setting on operations type form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:256 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:258 msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:260 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 msgid "Lots traceability" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:264 msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:265 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:267 msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:269 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:271 msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:272 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:274 msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:276 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:278 msgid "Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." msgstr "" @@ -2672,9 +3162,8 @@ msgstr "" msgid "Lots and serial numbers traceability report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:284 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:286 +msgid ":doc:`differences`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 @@ -2985,6 +3474,10 @@ msgstr "" msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 msgid "Shipping and receiving" msgstr "" @@ -3243,7 +3736,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 msgid "Create a sales order" msgstr "" @@ -4063,7 +4556,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 msgid "Create a purchase order" msgstr "" @@ -4073,7 +4566,7 @@ msgid "On the main :menuselection:`Purchase` application dashboard, start by mak msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:98 msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form — click it to reveal the associated receipt for the purchase order." msgstr "" @@ -4117,15 +4610,15 @@ msgstr "" msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:88 msgid "Deliver goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`New`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 msgid "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form — click it to reveal the associated delivery order for the sales order." msgstr "" @@ -4133,7 +4626,7 @@ msgstr "" msgid "The Delivery smart button appears after the sales order is confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:109 msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" @@ -4141,12 +4634,12 @@ msgstr "" msgid "Delivery Orders kanban card's 1 to Process smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 msgid "Process the delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 msgid "When viewing the delivery order (associated with the sales order above), click :guilabel:`Validate` to then complete the delivery." msgstr "" @@ -4154,7 +4647,7 @@ msgstr "" msgid "Validate the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:127 msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step." msgstr "" @@ -4352,34 +4845,38 @@ msgid "Activate multi-step routes and storage locations in Inventory settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 -msgid "Next, the warehouse needs to be configured for three-step receipts. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes." +msgid "Next, the warehouse needs to be configured for three-step receipts. To do that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select the desired warehouse to be edited. Doing so reveals the detail form for that specific warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 +msgid "On that :guilabel:`Warehouse` detail form page, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Set incoming shipment option to receive in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:37 -msgid "Activating three-step receipts and deliveries will create two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 +msgid "Activating three-step receipts and deliveries creates two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Inventory app --> Configuration --> Locations`, then click on the desired location to change (or update) the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:43 -msgid "Process a receipt in three steps (input + quality + stock)" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 +msgid "Receive in three steps (input + quality + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 -msgid "In the :menuselection:`Purchase` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 +msgid "To create a new :abbr:`RfQ (Request for Quotation)`, navigate to :menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ (Request for Quotation)` form page. On this page, select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "Process a receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 msgid "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." msgstr "" @@ -4388,15 +4885,15 @@ msgid "The status of the three receipt transfers will show which operation is re "are waiting another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 msgid "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 msgid "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" @@ -4404,7 +4901,7 @@ msgstr "" msgid "One Receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." msgstr "" @@ -4413,15 +4910,15 @@ msgid "Validate the receipt by clicking Validate, and the product will be transf "WH/Quality location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Process a transfer to Quality Control" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders." msgstr "" @@ -4429,15 +4926,15 @@ msgstr "" msgid "Validate the internal transfer to move the item to the Quality Control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 msgid "Process a transfer to stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." msgstr "" @@ -5688,6 +6185,118 @@ msgstr "" msgid "Once all the products have been picked, click on :guilabel:`Validate` to mark the batch transfer as :guilabel:`Done`." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:3 +msgid "Closest location removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:5 +msgid "For the *Closest Location* removal strategy, products are picked based on the alphanumeric order of storage location titles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:8 +msgid "The goal of this strategy is to save the warehouse worker from taking a long journey to a farther shelf when the product is also available at a closer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:13 +msgid ":doc:`About removal strategies `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:16 +msgid "To understand *location sequence* in the closest removal strategy, consider the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:19 +msgid "A product is stored in the following locations: `Shelf A/Pallet`, `Shelf A/Rack 1`, and `Shelf A/Rack 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:-1 +msgid "Show a mockup of real storage location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:26 +msgid "The sublocation, `Pallet`, is on the ground level. Products stored here are easier to retrieve, compared to requiring a forklift to reach `Rack 1` and `Rack 2`. The storage locations were strategically named in alphabetic order, based on ease of access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:31 +msgid "To use this removal strategy, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:35 +msgid ":ref:`Set up removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:40 +msgid "Location names" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:42 +msgid "To configure location names, begin by navigating to :menuselection:`Inventory app --> Configuration --> Locations`. Then, select an existing location, or click :guilabel:`New` to create a new one, and then enter the desired name in the :guilabel:`Location Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:46 +msgid "Once the locations are named in alphabetical order, based on their proximity to the output or packing location, set the removal strategy on the :ref:`parent location `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:50 +msgid "To do that, in the :guilabel:`Locations` list, select the parent location of the alphabetically named storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:53 +msgid "Doing so opens the form for the parent location. In the :guilabel:`Removal Strategy` field, select :guilabel:`Closest Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:57 +msgid "In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest to the packing area, where products retrieved from shelves are packed for shipment. The popular product, `iPhone charger` is stored in three locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:62 +msgid "To use closest location, set the removal strategy on the parent location, 'WH/Stock'." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:30 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:67 +msgid "To see how the closest location removal strategy works, consider the following example, featuring the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:71 +msgid "Fifteen, five, and thirty units are in stock at each respective location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:74 +msgid "To check the on-hand stock at each storage location, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:0 +msgid "Show on-hand stock at all locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:81 +msgid "Create a :ref:`delivery order ` for eighteen units of the `iPhone charger` by navigating to the :menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:84 +msgid "After adding the products, clicking :guilabel:`Confirm` creates a delivery order that reserves items stored at the closest location, using the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:87 +msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window that displays how the reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:91 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. All fifteen of the units stored at the closest location, `WH/Stock/Shelf 1`, are picked first. The remaining three units are then selected from the second closest location, `WH/Stock/Shelf 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:-1 +msgid "Display *Pick From* quantities for the order for iPhone chargers." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 msgid "Cluster picking" msgstr "" @@ -5777,6 +6386,7 @@ msgid "For the :guilabel:`Package Use` field, the :guilabel:`Disposable Box` opt msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 msgid ":ref:`Packages `" msgstr "" @@ -6056,73 +6666,511 @@ msgstr "" msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 -msgid "Count inventory by location" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 +msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 +msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 +msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 +msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 +msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 +msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Applied filters and group by on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 +msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 +msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 +msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 +msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 +msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 +msgid ":doc:`../inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:3 +msgid "FEFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:5 +msgid "The *First Expired, First Out* (FEFO) removal strategy targets products for removal based on their assigned removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:9 +msgid ":doc:`Other removal strategies `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:14 +msgid "Removal date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:16 +msgid "Products **must** be removed from inventory before their *removal date*, which is set as a certain number of days before the product's *expiration date*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:19 +msgid "The user sets this number of days by navigating to the product form's :guilabel:`Inventory` tab. Under the :guilabel:`Traceability` section, ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` or :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:23 +msgid "Next, select the :guilabel:`Expiration Date` option, which makes the :guilabel:`Removal Date` field (and other date fields) appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:27 +msgid "The :guilabel:`Lots and Serial Numbers` and :guilabel:`Expiration Dates` features **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings` to track expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:31 +msgid "The expiration date of a product is determined by adding the date the product was received to the number of days specified in the :guilabel:`Expiration Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:34 +msgid "The removal date takes this expiration date, and subtracts the number of days specified in the :guilabel:`Removal Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:38 +msgid ":doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:41 +msgid "In the :guilabel:`Inventory` tab of the product, `Egg`, the following :guilabel:`Dates` are set by the user:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:44 +msgid ":guilabel:`Expiration Date`: `30` days after receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:45 +msgid ":guilabel:`Removal Date`: `15` days before expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:-1 +msgid "Display expiration and removal dates set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:51 +msgid "A shipment of Eggs arrive at the warehouse on January 1st. So, the expiration date of the Eggs is **January 31st** (Jan 1st + 30). By extension, the removal date is **January 16th** (Jan 31 - 15)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:57 +msgid "To view the expiration dates of items in stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:60 +msgid "Next, click the additional options icon, located on the far-right, and select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:-1 +msgid "Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" +"smart button from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:71 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures that products with the nearest removal date are picked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:74 +msgid "To understand how this removal strategy works, consider the following example below about the product, `Carton of eggs`, which is a box containing twelve eggs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:77 +msgid "The product is tracked :guilabel:`By Lots`, and the product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First Out (FEFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:24 +msgid ":ref:`Set up force removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:25 +msgid ":ref:`Enable lots tracking `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:83 +msgid "`Odoo Tutorials: Perishable Products `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:35 +msgid "LOT1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:36 +msgid "LOT2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:37 +msgid "LOT3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:38 +msgid "On-hand stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:73 +msgid "5" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:75 +msgid "2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:96 +msgid "1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 +msgid "Expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:98 +msgid "April 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:99 +msgid "April 10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:100 +msgid "April 15" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:101 +msgid ":ref:`Removal date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:102 +msgid "February 26" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:103 +msgid "March 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:104 +msgid "March 9" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:106 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:109 +msgid "Clicking :guilabel:`Confirm` creates a delivery order for today, December 29th, and the lot numbers with the soonest expiration dates are reserved, using the :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:113 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the Carton of egg's product line, in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:117 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:120 +msgid "Since the order demanded six Cartons of eggs, using the :abbr:`FEFO (First Expired, First Out)` removal strategy, all five Cartons from `LOT1`, with the removal date of February 26th, are picked. The remaining Carton is selected from `LOT2`, which has a removal date of March 4th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:-1 +msgid "The stock moves window that shows the lots to be removed using FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:3 +msgid "FIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:5 +msgid "The *First In, First Out* (FIFO) removal strategy selects products with the earliest arrival dates. This method is useful for companies selling products that have short demand cycles, like clothes, for example. By using :abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock retention of specific styles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:11 +msgid ":doc:`Other removal methods `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:14 +msgid "Various quantities of the product, `T-shirt`, tracked by lot numbers, arrive on August 1st and August 25th. For an order made on September 1st, the :abbr:`FIFO (First In, First Out)` removal strategy prioritizes lots that have been in stock the longest. So, products received on August 1st are selected first for picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Illustration of FIFO selecting the oldest products in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:24 +msgid ":ref:`Lot/serial number setup details `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:29 +msgid "Arrival date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:31 +msgid "To see the product lot or serial number that arrived in inventory first, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:34 +msgid "Then, select the :guilabel:`▶️ (right-pointing arrow)` icon on the left of a product line, in order to reveal a list of the product's lots or serial numbers that are in stock. The :guilabel:`Created On` field shows the lot/serial number creation date, which is, essentially, the arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:39 +msgid "Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on December 29th, as displayed in the :guilabel:`Created On` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Display arrival date of a lot for an item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:49 +msgid "To understand how :abbr:`FIFO (First In, First Out)` rotates products out, consider the following example, focusing on three lots of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:52 +msgid "The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In, First Out)` is set as the :guilabel:`Force Removal Strategy`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:55 +msgid "The white shirts are tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:62 +msgid "The following table represents the on-hand stock and lot number details of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:74 +msgid "3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:42 +msgid ":ref:`Created on `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:77 +msgid "March 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:78 +msgid "April 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:79 +msgid "May 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:81 +msgid "To see the removal strategy in action, create a :ref:`delivery order ` for six white shirts by navigating to the :menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:84 +msgid "After clicking :guilabel:`Confirm` on the sales order, a delivery order with the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO (First In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:87 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the white shirt's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:91 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded six shirts, all five shirts from `LOT1`, and one shirt from `LOT2`, are selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:3 +msgid "Least packages removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:5 +msgid "The *Least Packages* removal strategy fulfills an order by opening the fewest number of packages, which is ideal for maintaining organized stock without needing to open multiple boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:10 +msgid "`Odoo Tutorials: Least Packages `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:12 +msgid "To understand how the removal strategy works, consider the following example, featuring a warehouse that stores packages of flour in bulk packages of `100 kg`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:15 +msgid "To minimize moisture, and/or prevent pests from entering open packages, the least packages removal strategy is used to pick from a single, opened package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:21 +msgid "A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some orders. There are other packages of `100 kg` in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:24 +msgid "When an order for `14 kg` of flour is placed, the package of `54 kg` is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:25 +msgid "When an order for *more* than `54 kg` of flour is placed, an unopened `100 kg` package is used to fulfill the order. While this temporarily results in two open packages, these open packages are prioritized in the next picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:32 +msgid "Using the least package removal strategy, the fewest number of packages is used to fulfill an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:35 +msgid "The :ref:`Packages feature ` **must** be enabled to use this strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:38 +msgid "Consider the following example, featuring the product, `Flour`. The product's :guilabel:`Units of Measure` field, located on the product form, is set to `kg`. The product is stored in packages of `100 kg`, with one remaining package containing `54 kg`. The product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:44 +msgid ":ref:`Set removal strategy on product category `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:47 +msgid "To check the product's on-hand stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:0 +msgid "Show on-hand stock in each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:54 +msgid "Create a :ref:`delivery order ` for eighty kilograms of flour by going to the :menuselection:`Sales app` and creating a new quotation. After clicking :guilabel:`Confirm`, the delivery order is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:58 +msgid "On the delivery order, the :guilabel:`Quantity` field displays the amount automatically picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:61 +msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window, displaying how the reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:65 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. Since the order demanded eighty kilograms, which exceeds the quantity in the opened package of `54 kg`, an unopened package of `100 kg` is selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 -msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:-1 +msgid "Show which package was picked in the *Pick From* field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 -msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:3 +msgid "LIFO removal" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Inventory adjustments page." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:5 +msgid "The *Last In, First Out* (LIFO) removal strategy picks the **newest** products on-hand, based on the date they entered a warehouse's stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 -msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:8 +msgid "Every time an order is placed for products using the :abbr:`LIFO (Last In, First Out)` strategy, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 -msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:16 +msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy is banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 -msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:19 +msgid "Consider the following example, with the product, `Cinder Block`, which is tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form. The :guilabel:`Force Removal Strategy` for the cinder block's product category is set to :guilabel:`Last In, First Out (LIFO)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 -msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:26 +msgid ":ref:`Check arrival date `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Applied filters and group by on inventory adjustments page." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:28 +msgid "The following table represents the cinder blocks in stock, and their various lot number details." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 -msgid "Change full inventory count frequency" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:43 +msgid "June 1" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 -msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:44 +msgid "June 3" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 -msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:45 +msgid "June 6" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Frequency field in inventory app settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:47 +msgid "To see the removal strategy in action, create a :ref:`delivery order ` for seven cinder blocks by navigating to the :menuselection:`Sales app` and creating a new quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 -msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:51 +msgid ":guilabel:`Confirm` the sales order to create a delivery order. Doing so reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 -msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:54 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the cinder block's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 -msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:58 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded seven cinder blocks, the newest cinder blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 -msgid ":doc:`../inventory_management/count_products`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:-1 +msgid "The detailed operations shows which lots are being selected for the picking." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 @@ -6430,381 +7478,232 @@ msgid "Storage Categories used in a variety of putaway rules." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:3 -msgid "Removal strategies (FIFO, LIFO, FEFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:7 -msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:13 -msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:17 -msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 -msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Change the Force Removal Strategy for either the Product Categories or Locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 -msgid "What happens inside the warehouse?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:35 -msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:40 -msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations." +msgid "Removal strategies" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:45 -msgid "Not all products have expiration dates, but in this example, expiration dates apply." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:5 +msgid "For companies with warehouses, *removal strategies* determine **which** products are taken from the warehouse, and **when**. For example, for perishable products, prioritizing the picking of goods with the nearest expiration date helps minimize food spoilage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Products entering stock via the receiving area." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:51 -msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 -msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:9 +msgid "The following columns in the table below list the removal strategies available in Odoo, and detail how pickings are determined along with the picking order. Leverage these removal strategies to have Odoo automatically select how products are selected for orders:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:64 -msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO `), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:18 +msgid ":doc:`FIFO `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n" -"account." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:19 +msgid ":doc:`LIFO `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:79 -msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either the :ref:`Two-step delivery ` or :ref:`Three-step delivery ` documentation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:20 +msgid ":doc:`FEFO `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:85 -msgid "How each removal strategy works" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 +msgid ":doc:`Closest Location `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 -msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:22 +msgid ":doc:`Least Packages `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 -msgid "First In, First Out (FIFO)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:23 +msgid "Based on" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:92 -msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:25 +msgid ":ref:`Incoming date `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 -msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:26 +msgid ":ref:`Removal date `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:99 -msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:27 +msgid ":ref:`Location sequence `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:102 -msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:28 +msgid ":ref:`Package quantity `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations for the transfer shows the nail lots to be removed." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:29 +msgid "Selection order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 -msgid "Last In, First Out (LIFO)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:30 +msgid "First in" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:114 -msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:31 +msgid "Last in" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 -msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:32 +msgid ":ref:`First to expire `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 -msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 +msgid ":ref:`Alphanumeric name of location `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:126 -msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:34 +msgid "Quantity closest to fulfilling demand" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 -msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:36 +msgid "For comprehensive examples for how to use each removal strategy, refer to each individual documentation page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:132 -msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:44 +msgid "Removal strategies are set on either the product category or storage location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations shows which lots are being selected for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 -msgid "First Expired, First Out (FEFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 -msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 -msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:150 -msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:153 -msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:157 -msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`." +msgid "Change the Force Removal Strategy for either the Product Categories or Locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations for the transfer shows the lots to be removed." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:50 +msgid "Configure removal strategies on the location by going to :menuselection:`Inventory --> Configuration --> Locations`, and selecting the desired location. On the location form, choose a removal strategy from the :guilabel:`Removal Strategy` field's drop-down menu options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:167 -msgid "Using removal strategies" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:55 +msgid "To set a removal strategy on a location, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 -msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 +msgid "These features are **only** necessary when setting the removal strategy on a location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid ":alt: Traceability settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:61 +msgid "Configure removal strategies on product categories by going to :menuselection:`Inventory --> Configuration --> Product Categories` and selecting the intended product category. Next, choose a removal strategy from the :guilabel:`Force Removal Strategy` drop-down menu options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid ":alt: Warehouse settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:66 +msgid "When there are different removal strategies applied on both the location and product category for a product, the value set on the :guilabel:`Force Removal Strategy` field set on a :guilabel:`Product Category` form is applied as top priority." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:183 -msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:91 +msgid "Required features" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:189 -msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:73 +msgid "While some removal strategies are available by default, some additional features **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings` for the removal strategy option to appear in the drop-down menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal Strategy` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:194 -msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:78 +msgid "Refer to the table below for a summary of required features. Otherwise, refer to the dedicated sections for the removal strategy for more details on requirements and usage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:198 -msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure `). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:86 +msgid "FIFO" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:204 -msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 +msgid "LIFO" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:213 -msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:88 +msgid "FEFO" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:218 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:89 msgid "Closest Location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:220 -msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:224 -msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:230 -msgid "Use removal strategies" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:232 -msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Removal strategy on a product category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:241 -msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n" -"numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:252 -msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`⦙≣ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:260 -msgid "FIFO (First In, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:262 -msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:267 -msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the lots of white shirts in the inventory valuation report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:275 -msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 +msgid "Least Packages" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:278 -msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:93 +msgid "Lots & Serial Numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:285 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:94 +msgid "Lots & Serial Numbers, Expiration Date" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Two lots being reserved for a sales order with the FIFO strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:95 +msgid "Storage Locations, Multi-Step Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:295 -msgid "LIFO (Last In, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 +msgid "Packages" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:297 -msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:101 +msgid "Lots and serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:302 -msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:103 +msgid "Lots and serial numbers differentiate identical products and track information like arrival or expiration dates. To enable this feature, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots & Serial Numbers` to enable the feature." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the lots of cinder blocks in the inventory valuation report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:310 -msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks." +msgid "Enable lots and serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:313 -msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 +msgid "Next, ensure the intended product is tracked by lots or serial numbers by navigating to the product form through :menuselection:`Inventory --> Products --> Products`, and selecting the desired product. On the product form, switch to the :guilabel:`Inventory` tab, and under the :guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:318 -msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 +msgid "After enabling the features, assign lot or serial numbers to products using an :doc:`inventory adjustment <../inventory_management/count_products>` or during :ref:`product reception `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Last in first out (LIFO) strategy set up as forced removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 +msgid "Locations and routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:325 -msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:125 +msgid "**Storage locations** and **multi-step routes** are necessary features for setting **all** types of removal strategies on a location. However, these features are specifically required for the closest location removal strategy since it is only applied at the location level." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:332 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 +msgid "To activate these features, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Warehouse` heading, enable the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` features." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Two lots being reserved for sale with the LIFO strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:344 -msgid "FEFO (First Expired, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:346 -msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:352 -msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates." +msgid "Enable the locations and route features." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:358 -msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:362 -msgid "For more information about expiration dates, reference the :doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>` document." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:365 -msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:370 -msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:374 -msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View the hand cream lot numbers and expiration dates in the inventory report." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 +msgid "Enable the **expiration date** feature to track expiration dates, best before dates, removal dates, and alert dates on a lot or serial number by navigating to :menuselection:`Inventory --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:382 -msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 +msgid "Under the :guilabel:`Traceability` heading, ensure the :guilabel:`Lots & Serial Numbers` feature is selected, and then select the check box for :guilabel:`Expiration Dates` to enable the feature." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the removal date for 0000001." +msgid "Enable expiration dates feature for FEFO." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:391 -msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:158 +msgid "The *packages* feature is used to group products together and is required for the least packages removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:396 -msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:161 +msgid "Navigate to :menuselection:`Inventory --> Configuration --> Settings` and select the check box for the :guilabel:`Packages` feature." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "FEFO forced removal strategy set on the product category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:403 -msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgid "Enable the packages feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:410 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the sales order." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:170 +msgid ":doc:`2-step delivery <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Hand cream lot numbers selected for the sales order." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:171 +msgid ":doc:`3-step delivery <../../shipping_receiving/daily_operations/delivery_three_steps>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 @@ -7092,10 +7991,6 @@ msgstr "" msgid ":ref:`Use Different Units of Measure `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 -msgid "Packages" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:68 msgid "Packages are a physical container that holds one or several products from a picking, typically used for outgoing deliveries or internal transfers. Packages can be a reusable or disposable (shipping) box, and are **not** specific to a product." msgstr "" @@ -7903,26 +8798,26 @@ msgid ":guilabel:`Barcode`: the barcode number assigned to the location" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 -msgid ":guilabel:`Removal Strategy`: the :ref:`strategy ` for how items should be taken from inventory" +msgid ":guilabel:`Removal Strategy`: the :doc:`strategy <../advanced_operations_warehouse/removal>` for how items should be taken from inventory" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 msgid "The form for creating a new location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 msgid "Create location hierarchies" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse or another location. Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a virtually infinite hierarchical structure." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 msgid "Location hierarchy could be organized so that a shelf is located within an aisle, which is located within a room, which is located within the overall warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 msgid "To create the location hierarchy in the example above, set the warehouse as the parent of the room, the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted to a hierarchy of any magnitude." msgstr "" @@ -9704,7 +10599,7 @@ msgid "Managing BoMs for product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 -msgid "Odoo allows one bill of materials (BoM) to be used for multiple variants of the same product. Having a consolidated BoM for a product with variants saves time by preventing the need to manage multiple BoMs." +msgid "Odoo allows one bill of materials (BoM) to be used for multiple variants of the same product. Having a consolidated :abbr:`BoM (bill of materials)` for a product with variants saves time by preventing the need to manage multiple :abbr:`BoMs (bills of materials)`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 @@ -9712,35 +10607,199 @@ msgid "Activate product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 -msgid "To activate variants, simply navigate to :menuselection:`Inventory --> Configuration --> Settings --> Products`, and then enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting. For more information on configuring product variants, refer to :doc:`this page <../../../sales/sales/products_prices/products/variants>`." +msgid "To activate the product variants feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Products` section. Then, click the checkbox to enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:17 +msgid "For more information on configuring product variants, refer to the :doc:`product variants <../../../sales/sales/products_prices/products/variants>` documentation." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 msgid "Selecting \"Variants\" from Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:22 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 +msgid "Create custom product attributes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:27 +msgid "Once the product variants feature is activated, create and edit product attributes on the :guilabel:`Attributes` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:30 +msgid "The :guilabel:`Attributes` page is accessible either from :menuselection:`Inventory app --> Configuration --> Settings` by clicking the :guilabel:`Attributes` button, or by clicking :menuselection:`Inventory app --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:34 +msgid "Once on the :guilabel:`Attributes` page, either click into an existing attribute, or click :guilabel:`Create` to create a new one. Clicking :guilabel:`Create` reveals a new, blank form for customizing an attribute. For an existing attribute, click :guilabel:`Edit` on its form to make changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +msgid "Assign an :guilabel:`Attribute Name`, and choose a category from the :guilabel:`Category` field's drop-down menu. Then, select the desired options next to the :guilabel:`Display Type` and :guilabel:`Variants Creation Mode` fields. Once the desired options are selected, click :guilabel:`Add a line` under the :guilabel:`Attribute Values` tab to add a new value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:45 +msgid "Included on the :guilabel:`Value` row is a :guilabel:`Is custom value` checkbox. If selected, this value will be recognized as a custom value, which allows customers to type special customization requests upon ordering a custom variant of a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:0 +msgid "Product variant attribute configuration screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:54 +msgid "Once all desired :guilabel:`Values` have been added, click :guilabel:`Save` to save the new attribute." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:58 +msgid "Add product variants on the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:60 +msgid "Created attributes can be applied on specific variants for particular products. To add product variants to a product, navigate to the product form by going to :menuselection:`Inventory app --> Products --> Products`. To make changes to the product, click :guilabel:`Edit`. Then, click the :guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:65 +msgid "Under the :guilabel:`Attribute` header, click :guilabel:`Add a line` to add a new attribute, and select one to add from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:68 +msgid "Then, under the :guilabel:`Values` header, click the drop-down menu to choose from the list of existing values. Click on each desired value to add them, and repeat this process for any additional attributes that should be added to the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:72 +msgid "Once finished, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +msgid "Product form variants tab with values and attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:79 +msgid ":abbr:`BoM (bill of materials)` products with multiple variants that are manufactured in-house should either have a **0,0 reordering rule** set up, or have their replenishment routes set to *Replenish on Order (MTO)*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:84 msgid "Apply BoM components to product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:24 -msgid "Next, create a new BoM or edit an existing one by going to :menuselection:`Manufacturing --> Products --> Bills of Materials`. Then, click :guilabel:`Edit`. The :guilabel:`Apply on Variants` option to assign components to specific product variants on the BoM is available once the :guilabel:`Variants` setting is activated from the :guilabel:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:86 +msgid "Next, create a new :abbr:`BoM (bill of materials)`. Or, edit an existing one, by going to :menuselection:`Manufacturing app --> Products --> Bills of Materials`. Then, click :guilabel:`Create` to open a new :guilabel:`Bills of Materials` form to configure from scratch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:90 +msgid "Add a product to the :abbr:`BoM (bill of materials)` by clicking the drop-down menu in the :guilabel:`Product` field and selecting the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:93 +msgid "Then, add components by clicking :guilabel:`Add a line` under the :guilabel:`Component` section of the :guilabel:`Components` tab, and choosing the desired components from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:96 +msgid "Choose the desired values in the :guilabel:`Quantity` and :guilabel:`Product Unit of Measure` columns. Then, choose the desired values in the :guilabel:`Apply on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:100 +msgid "The :guilabel:`Apply on Variants` option to assign components to specific product variants on the :abbr:`BoM (bill of materials)` is available once the :guilabel:`Variants` setting is activated from the :menuselection:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu (three-dots icon, to the right of the header row)." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 msgid "\"Apply on Variants\" option on the additional options menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:110 msgid "Each component can be assigned to multiple variants. Components with no variants specified are used in every variant of the product. The same principle applies when configuring operations and by-products." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 -msgid "When defining variant BoMs by component assignment, the :guilabel:`Product Variant` field in the main section of the BoM should be left blank, as shown below. This field is used only when creating a BoM specifically for one product variant." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:114 +msgid "When defining variant :abbr:`BoMs (bills of material)` by component assignment, the :guilabel:`Product Variant` field in the main section of the :abbr:`BoM (bill of materials)` should be left blank. This field is *only* used when creating a :abbr:`BoM (bill of materials)` specifically for one product variant." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:119 +msgid "When all desired configurations have been made to the :abbr:`BoM (bill of materials)`, click :guilabel:`Save` at the top of the form to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:123 +msgid "For components that only apply for specific variants, choose which operations the components should be consumed in. If the :guilabel:`Consumed in Operation` column is *not* immediately visible, activate it from the additional options menu (three-dots icon, to the right of the header row)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:129 +msgid "Sell and manufacture variants of BoM products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:131 +msgid "To sell and manufacture variants of :abbr:`BoM (bill of materials)` products to order, navigate to :menuselection:`Sales app --> Create` to create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:135 +msgid "Sell variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:137 +msgid "Once on the blank :guilabel:`Quotation` form, click the drop-down next to the :guilabel:`Customer` field to add a customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:140 +msgid "Then, under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the previously-created :abbr:`BoM (bill of materials)` product with variants from the drop-down menu. Doing so reveals a :guilabel:`Configure a product` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:144 +msgid "From the pop-up window, click the desired attribute options to configure the correct variant of the product to manufacture. Then, click the green :guilabel:`+` or :guilabel:`-` icons next to the `1` to change the quantity to sell and manufacture, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +msgid "Configure a product pop-up for choosing variant attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:152 +msgid "Once all the specifications have been chosen, click :guilabel:`Add`. This will change the pop-up to a second :guilabel:`Configure` pop-up, where available optional products will appear, if they have been created previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:156 +msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:158 +msgid "Then, click :guilabel:`Save` to save all changes, and click :guilabel:`Confirm` at the top of the :guilabel:`Quotation` form to create and confirm a new sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:162 +msgid "Manufacture variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:164 +msgid "Once the :abbr:`SO (sales order)` is confirmed, a :guilabel:`Manufacturing` smart button appears at the top of the :abbr:`SO (sales order)` form. Click the :guilabel:`Manufacturing` smart button to open the :guilabel:`Manufacturing Order` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:168 +msgid "On this form, under the :guilabel:`Components` tab, the appropriate components for the chosen variant are listed. And, depending on the variant, different components will be listed. To see any mandatory or optional :guilabel:`Operation` steps, click the :guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:172 +msgid "To enter the tablet view work order screen, click the :guilabel:`tablet icon` to the right of the row for the desired operation to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:175 +msgid "From the tablet view, click :guilabel:`Mark as Done` as the operation progresses to complete the operation steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:178 +msgid "Alternatively, click the :guilabel:`Mark as Done` button at the top of the manufacturing order form to complete the order." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 -msgid "Applying components to multiple variants." +msgid "Manufacturing order for variant of BoM product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:185 +msgid "Then, navigate back to the :abbr:`SO (sales order)` via the breadcrumbs at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:187 +msgid "Now that the product has been manufactured, click the :guilabel:`Delivery` smart button to deliver the product to the customer. From the :guilabel:`Delivery Order` form, click :guilabel:`Validate`, then click :guilabel:`Apply` to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:191 +msgid "To finish the sale, click back to the :abbr:`SO (sales order)` via the :guilabel:`breadcrumbs` at the top of the page again. Then, click :guilabel:`Create Invoice` followed by :guilabel:`Create Invoice` again to invoice the customer for the order." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:3 @@ -10127,10 +11186,6 @@ msgstr "" msgid "If managing the replenishment of raw materials **B** at your subcontractor’s location is not needed, simply include the cost of **B** in the subcontractor’s price **s** and remove the products *B* from the *BoM*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 -msgid "Traceability" -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 msgid "In case the received products from the subcontractor contain tracked components, their serial or lot numbers need to be specified during the receipt." msgstr "" diff --git a/locale/sources/legal.pot b/locale/sources/legal.pot index e182155fdf..1aba3db0f6 100644 --- a/locale/sources/legal.pot +++ b/locale/sources/legal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-08 08:46+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -272,6 +272,7 @@ msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:12 -msgid "Esta es una traducción al español del \"Odoo Enterprise Subscription Agreement\". Esta traducción se proporciona con la esperanza de que facilite la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Enterprise Subscription Agreement\" es :ref:`la versión original en inglés `" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_es.rst:21 +#: ../../content/legal/terms/i18n/enterprise_es.rst:18 msgid "Al suscribirse a los servicios de Odoo Enterprise (en adelante “los Servicios”) proporcionados por Odoo SA y sus filiales (en adelante denominadas conjuntamente “Odoo SA”), relacionados con las versiones Odoo Enterprise o Odoo community (en adelante “el Software”) y alojados en los servidores de la nube de Odoo SA (en adelante “Servicio en la Nube”) o en servidores locales (en adelante “Auto-hospedaje”), usted (en adelante “el Cliente”) acepta los términos y condiciones establecidos a continuación (en adelante “el Acuerdo”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:31 +#: ../../content/legal/terms/i18n/enterprise_es.rst:28 msgid "1 Término del Acuerdo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:33 +#: ../../content/legal/terms/i18n/enterprise_es.rst:30 msgid "La duración de la suscripción (en adelante el “Plazo”) será indicada por escrito en este Acuerdo, y comenzará a partir de la fecha de firma del Acuerdo. La suscripción se considerará renovada automáticamente por un período igual al Plazo estipulado originalmente, salvo que alguna de las partes del Acuerdo proporcione un aviso por escrito expresando su deseo de culminar los Servicios al menos 30 días antes de la fecha de culminación del Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:42 +#: ../../content/legal/terms/i18n/enterprise_es.rst:39 msgid "2 Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:48 +#: ../../content/legal/terms/i18n/enterprise_es.rst:45 msgid "Usuario" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:45 +#: ../../content/legal/terms/i18n/enterprise_es.rst:42 msgid "El término usuario hace referencia a cualquier cuenta de usuario identificada como activa en el Software, con potestates de creación y/o edición. No se consideran como Usuarios a las cuentas desactivadas y aquellas cuentas utilizadas por personas (o sistemas) que solo tienen acceso limitado al Software a través del portal del usuario." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:53 +#: ../../content/legal/terms/i18n/enterprise_es.rst:49 msgid "Aplicación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:51 -msgid "Una ‘aplicación’ es un grupo especializado de funciones disponibles para ser instaladas en el Software, las cuales están enunciadas en la sección de Precios del `sitio web de Odoo SA `__" +#: ../../content/legal/terms/i18n/enterprise_es.rst:48 +msgid "Una ‘Aplicación’ es un grupo especializado de funciones disponibles para ser instaladas en el Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:59 +#: ../../content/legal/terms/i18n/enterprise_es.rst:55 msgid "Partner de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:56 +#: ../../content/legal/terms/i18n/enterprise_es.rst:52 msgid "Un ‘Partner’ de Odoo es una empresa o individuo externo a Odoo SA que ofrece servicios relacionados con el Software, y quien ha sido seleccionado por el Cliente para trabajar directamente con él. En cualquier momento, el cliente puede decidir trabajar con un Partner diferente o con Odoo SA directamente (sujeto a previo aviso)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:66 -msgid "Módulo adicional" -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_es.rst:62 -msgid "Un módulo adicional es un directorio de archivos de código fuente, o un conjunto de personalizaciones basadas en lenguaje de programación Python, creadas en una base de datos (por ejemplo, con Odoo Studio), que agrega características o cambia el comportamiento estándar de Software. Pueden haber sido desarrolladas por el Cliente, por Odoo SA, por un Partner de Odoo en nombre del Cliente o por terceros." +msgid "Módulo Adicional" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:71 -msgid "Módulo adicional de mantenimiento" +#: ../../content/legal/terms/i18n/enterprise_es.rst:58 +msgid "Un Módulo Adicional es un directorio de archivos de código fuente, o un conjunto de personalizaciones basadas en lenguaje de programación Python, creadas en una base de datos (por ejemplo, con Odoo Studio), que agrega características o cambia el comportamiento estándar de Software. Pueden haber sido desarrolladas por el Cliente, por Odoo SA, por un Partner de Odoo en nombre del Cliente o por terceros." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:69 -msgid "Un módulo adicional de mantenimiento es un módulo adicional por el cual el Cliente ha elegido pagar un costo de mantenimiento con el fin de obtener servicios de soporte, actualizaciones y corrección de errores." +#: ../../content/legal/terms/i18n/enterprise_es.rst:67 +msgid "Módulo Adicional Cubierto" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:80 -msgid "Error/Bug" +#: ../../content/legal/terms/i18n/enterprise_es.rst:65 +msgid "Un Módulo Adicional Cubierto es un Módulo Adicional por el cual el Cliente ha elegido pagar un costo de mantenimiento con el fin de obtener servicios de soporte, actualizaciones y corrección de Bugs." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:74 -msgid "Se considera como ‘bug’ a cualquier falla del Software o de un módulo adicional de mantenimiento que resulte en una disrupción completa, una cadena de errores o un fallo de seguridad, y que no es causado directamente por una instalación o configuración defectuosa. El incumplimiento de algunas especificaciones o requisitos será considerado como un Bug a la discreción de Odoo SA (por ejemplo, cuando el Software no cumple con el comportamiento ni los resultados para el cual fue diseñado, o cuando una característica específica del país deja de cumplir los requisitos legales de contabilidad)." +#: ../../content/legal/terms/i18n/enterprise_es.rst:70 +msgid "Se considera un Bug cualquier falla del Software o de un Módulo Adicional Cubierto que resulte en una parada completa, mensaje de error de fallo, o un fallo de seguridad, y que no es causado directamente por una instalación o configuración defectuosa. El incumplimiento de algunas especificaciones o requisitos será considerado como un Bug a la discreción de Odoo SA (por ejemplo, cuando el Software no cumple con el comportamiento ni los resultados para el cual fue diseñado, o cuando una característica específica del país deja de cumplir los requisitos legales de contabilidad)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:85 +#: ../../content/legal/terms/i18n/enterprise_es.rst:81 msgid "Versiones Cubiertas" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:83 +#: ../../content/legal/terms/i18n/enterprise_es.rst:79 msgid "A menos que se especifique lo contrario, los Servicios proporcionados por en virtud de este Acuerdo son únicamente aplicables a las versiones cubiertas del Software, las cuales incluyen las últimas tres (3) versiones publicadas." msgstr "" +#: ../../content/legal/terms/i18n/enterprise_es.rst:85 +msgid "Plan de Suscripción" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_es.rst:84 +msgid "Un Plan de Suscripción define un conjunto de Aplicaciones, funciones y soluciones de alojamiento cubiertas por este Acuerdo, y se define por escrito al concluir este Acuerdo." +msgstr "" + #: ../../content/legal/terms/i18n/enterprise_es.rst:90 msgid "3 Acceso al Software" msgstr "" @@ -1576,7 +1577,7 @@ msgid "Durante la vigencia de este Acuerdo, Odoo SA le otorga al Cliente una lic msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:102 -msgid "El Cliente acepta tomar todas las medidas necesarias para garantizar que no se modificará la parte del Software que ejecuta y verifica el uso y la recolección de estadísticas válidas, incluyendo pero sin limitarse a la ejecución de una instancia, el número de usuarios, las aplicaciones instaladas y el número de líneas de códigos incluidas en los módulos adicionales de mantenimiento." +msgid "El Cliente acepta tomar todas las medidas necesarias para garantizar que no se modificará la parte del Software que ejecuta y verifica el uso y la recolección de estadísticas válidas, incluyendo pero sin limitarse a la ejecución de una instancia, el número de usuarios, las aplicaciones instaladas y el número de líneas de códigos incluidas en los Módulos Adicionales Cubiertos." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:107 @@ -1588,7 +1589,7 @@ msgid "Después de la expiración o terminación de este Acuerdo, la licencia co msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:115 -msgid "En caso de que exista algún incumplimiento por parte del Cliente a los términos de esta sección, el Cliente acuerda indemnizar a Odoo SA una cuota adicional equivalente al 300% del precio aplicable por el número actual de usuarios y aplicaciones instaladas." +msgid "En caso de que exista algún incumplimiento por parte del Cliente a los términos de esta sección, el Cliente acuerda indemnizar a Odoo SA una cuota adicional equivalente al 300% del precio aplicable por el número actual de usuarios." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:122 @@ -1600,7 +1601,7 @@ msgid "4.1 Servicio de corrección de Bugs" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:129 -msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a hacer todos los esfuerzos razonables para remediar cualquier Bug presente en el Software y los Módulos adicionales de mantenimiento, que haya reportado el Cliente a través del medio apropiado (como el formulario del sitio web o vía llamada telefónica a los numeros enlistados en `Odoo Help `__, o cuando se trabaja con un Partner a través del medio establecido por el Partner), y a manejar las solicitudes del Cliente dentro de 2 días hábiles posteriores a la creación del reporte por parte del Cliente." +msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a hacer todos los esfuerzos razonables para remediar cualquier Bug presente en el Software y los Módulos Adicionales Cubiertos, que haya reportado el Cliente a través del medio apropiado (como el formulario del sitio web o vía llamada telefónica a los numeros enlistados en `Odoo Help `__, o cuando se trabaja con un Partner a través del medio establecido por el Partner), y a manejar las solicitudes del Cliente dentro de 2 días hábiles posteriores a la creación del reporte por parte del Cliente." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:137 @@ -1612,7 +1613,7 @@ msgid "Cuando se corrige un Bug de cualquiera de las versiones cubiertas, Odoo S msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:144 -msgid "Las partes de este Acuerdo reconocen que Odoo SA no es responsable de los Bugs en el Software o en los módulos adicionales de mantenimiento de conformidad con lo establecido en la sección 7.3 de este Acuerdo y en la licencia del Software." +msgid "Las partes de este Acuerdo reconocen que Odoo SA no es responsable de los Bugs en el Software o en los Módulos Adicionales Cubiertos de conformidad con lo establecido en la sección 7.3 de este Acuerdo y en la licencia del Software." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:149 @@ -1664,7 +1665,7 @@ msgid "El Servicio de Actualización se limita a la conversión técnica y adapt msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:205 -msgid "El Cliente tiene la responsabilidad de verificar y validar la base de datos actualizada para detectar bugs, analizar e impacto de los cambios y las nuevas funcionalidades implementadas en la Versión Deseada, y de convertir y adaptar cualquier extensión del Software desarrollada por terceros que haya sido instalada antes de la actualización a la Versión Deseada (por ejemplo, módulos adicionales sin mantenimiento de Odoo). El Cliente puede enviar múltiples solicitudes de actualización de una base de datos hasta que se haya logrado un resultado aceptable." +msgid "El Cliente tiene la responsabilidad de verificar y validar la base de datos actualizada para detectar Bugs, analizar e impacto de los cambios y las nuevas funcionalidades implementadas en la Versión Deseada, y de convertir y adaptar cualquier extensión del Software desarrollada por terceros que haya sido instalada antes de la actualización a la Versión Deseada (por ejemplo, módulos adicionales sin mantenimiento de Odoo). El Cliente puede enviar múltiples solicitudes de actualización de una base de datos hasta que se haya logrado un resultado aceptable." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:215 @@ -1708,7 +1709,7 @@ msgid "Alcance" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:239 -msgid "Durante la vigencia del presente Acuerdo, el Cliente puede crear un número ilimitado de tickets de soporte sin costos adicionales, exclusivamente para preguntas relacionadas a Bugs (consultar sección :ref:`bugfix_es`) u orientación en cuanto al uso de las funcionalidades estándares del Software y de los módulos adicionales de mantenimiento." +msgid "Durante la vigencia del presente Acuerdo, el Cliente puede crear un número ilimitado de tickets de soporte sin costos adicionales, exclusivamente para preguntas relacionadas a Bugs (consultar sección :ref:`bugfix_es`) u orientación en cuanto al uso de las funcionalidades estándares del Software y de los Módulos Adicionales Cubiertos." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:244 @@ -1732,11 +1733,11 @@ msgid "Para la corrección de Bugs, soporte y servicios de actualización, el Cl msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:264 -msgid "Odoo SA subcontratará los servicios relacionados a los Módulos adicionales de mantenimiento al Partner de Odoo, quien se convierte en el principal punto de contacto del Cliente en caso que el Cliente decida trabajar con un Partner de Odoo. El Partner de Odoo puede contactar a Odoo SA en nombre del Cliente para obtener asistencia de segundo nivel con respecto a las características estándar del Software." +msgid "Odoo SA subcontratará los servicios relacionados a los Módulos Adicionales Cubiertos al Partner de Odoo, quien se convierte en el principal punto de contacto del Cliente en caso que el Cliente decida trabajar con un Partner de Odoo. El Partner de Odoo puede contactar a Odoo SA en nombre del Cliente para obtener asistencia de segundo nivel con respecto a las características estándar del Software." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:270 -msgid "Si el cliente decide trabajar con Odoo SA directamente, los servicios relacionados con los módulos adicionales de mantenimiento serán cubiertos por Odoo SA siempre que el Cliente esté alojado en la plataforma de la nube de Odoo." +msgid "Si el cliente decide trabajar con Odoo SA directamente, los servicios relacionados con los Módulos Adicionales Cubioertos serán cubiertos por Odoo SA siempre que el Cliente esté alojado en la plataforma de la nube de Odoo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:277 @@ -1748,322 +1749,322 @@ msgid "5.1 Cargos estándares" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:284 -msgid "Los cargos estándares de la suscripción de Odoo Enterprise y los Servicios están basados en la cantidad de Usuarios y las Aplicaciones instaladas que utiliza el Cliente y se especifican por escrito al concluir el Acuerdo." +msgid "Los cargos estándares de la suscripción de Odoo Enterprise y los Servicios están basados en la cantidad de Usuarios y el Plan de Suscripción utilizado por el Cliente, y se especifican por escrito al concluir el Acuerdo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:288 -msgid "Si el Cliente tiene más usuarios o aplicaciones instaladas durante el Plazo que las especificadas en el momento de la celebración de este Acuerdo, el Cliente acepta pagar (al inicio del nuevo Plazo) una tarifa adicional equivalente al precio aplicable de conformidad con la lista de precios por aquellos usuarios o aplicaciones adicionales, por el resto del Plazo." +msgid "Si durante el Plazo del Acuerdo, el Cliente tiene más Usuarios o utiliza funciones que requieren otro Plan de Suscripción diferente al especificado en el momento de la conclusión de este Acuerdo, el Cliente acepta pagar una tarifa adicional equivalente al precio aplicable de conformidad con la lista de precios (en el momento de la desviación del número especificado de Usuarios o del Plan de Suscripción) por los Usuarios adicionales o el Plan de Suscripción requerido, por el resto del Plazo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:293 -msgid "Además, los servicios de los módulos adicionales de mantenimiento se cobran en función al número de líneas de código de estos módulos. Cuando el cliente opta por el mantenimiento de estos módulos adicionales de mantenimiento, el costo es una tarifa mensual de 16 € por 100 líneas de código (redondeadas a las siguientes 100), al menos que se especifique lo contrario por escrito al celebrar este Acuerdo. Las líneas de código serán contadas con el comando ‘cloc’ del Software, e incluyen todas las líneas de texto en el código fuente de esos módulos, independientemente del lenguaje de programación (Python, Javascript, XML, etc), excluyendo líneas en blanco, comentarios y archivos que no se cargan al instalar o ejecutar el software." +#: ../../content/legal/terms/i18n/enterprise_es.rst:295 +msgid "Además, los servicios de los Módulos Adicionales Cubiertos se cobran en función al número de líneas de código de estos módulos. Cuando el cliente opta por el mantenimiento de Módulos Adicionales Cubiertos, el costo es una tarifa mensual de 16 € por 100 líneas de código (redondeadas a las siguientes 100), al menos que se especifique lo contrario por escrito al celebrar este Acuerdo. Las líneas de código serán contadas con el comando ‘cloc’ del Software, e incluyen todas las líneas de texto en el código fuente de esos módulos, independientemente del lenguaje de programación (Python, Javascript, XML, etc), excluyendo líneas en blanco, comentarios y archivos que no se cargan al instalar o ejecutar el software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:302 -msgid "Cuando el Cliente solicita una actualización, por cada módulo adicional de mantenimiento que no haya sido cubierto por los costos de mantenimiento durante los últimos 12 meses, Odoo SA puede cobrar una tarifa adicional única de 16 € por cada 100 líneas de código, por cada mes faltante de cobertura." +#: ../../content/legal/terms/i18n/enterprise_es.rst:304 +msgid "Cuando el Cliente solicita una actualización, por cada Módulo Adicional Cubierto que no haya sido cubierto por los costos de mantenimiento durante los últimos 12 meses, Odoo SA puede cobrar una tarifa adicional única, por cada mes faltante de cobertura." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:309 +#: ../../content/legal/terms/i18n/enterprise_es.rst:311 msgid "5.2 Cargos de renovación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:311 -msgid "Siguiendo la renovación descrita en la sección :ref:`term_es` del presente Acuerdo, si los cargos aplicados durante el Plazo anterior (excluyendo cualquier “Descuento para usuarios iniciales”) son más bajos que el precio aplicable en la lista de precios actual, dichos cargos podrán aumentar 7% como máximo." +#: ../../content/legal/terms/i18n/enterprise_es.rst:313 +msgid "Siguiendo la renovación descrita en la sección :ref:`term_es` del presente Acuerdo, si los cargos aplicados durante el Plazo anterior son más bajos que el precio aplicable en la lista de precios actual, dichos cargos podrán aumentar 7% como máximo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:319 +#: ../../content/legal/terms/i18n/enterprise_es.rst:321 msgid "5.3 Impuestos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:321 +#: ../../content/legal/terms/i18n/enterprise_es.rst:323 msgid "Todas las tarifas y cargos son exclusivos de todos los impuestos, tarifas o cargos federales, provinciales, estatales, locales o gubernamentales aplicables (conjuntamente los “Impuestos”). El Cliente es responsable de pagar todos los Impuestos asociados con las compras realizadas por el Cliente en virtud de este Acuerdo, excepto cuando Odoo SA esté legítimamente obligado a pagar o recolectar los Impuestos que el Cliente debe asumir." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:330 +#: ../../content/legal/terms/i18n/enterprise_es.rst:332 msgid "6 Condiciones de los servicios" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:333 +#: ../../content/legal/terms/i18n/enterprise_es.rst:335 msgid "6.1 Obligaciones del cliente" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:335 +#: ../../content/legal/terms/i18n/enterprise_es.rst:337 msgid "El Cliente se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:337 +#: ../../content/legal/terms/i18n/enterprise_es.rst:339 msgid "Pagar a Odoo SA cualquier cargo aplicable por los Servicios del presente Acuerdo, según las condiciones de pago especificadas en la factura correspondiente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:341 -msgid "Notificar inmediatamente a Odoo SA cuando su número real de usarios o aplicaciones instaladas exceda el número especificado al final del Acuerdo y, en este caso, el pago de la tarifa adicional aplicable como se describe en la sección :ref:`charges_standard_es`;" +#: ../../content/legal/terms/i18n/enterprise_es.rst:343 +msgid "Notificar inmediatamente a Odoo SA cuando su número real de Usarios exceda la cantidad especificada al momento de la conclusión del Acuerdo, y en este caso, pagar la tarifa adicional aplicable como se describe en la sección :ref:`charges_standard_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:346 +#: ../../content/legal/terms/i18n/enterprise_es.rst:348 msgid "Tomar todas las medidas necesarias para garantizar la ejecución no modificada de la parte del Software que verifica la validez del uso de Odoo Enterprise Edition, como se describe en la sección :ref:`enterprise_access_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:350 +#: ../../content/legal/terms/i18n/enterprise_es.rst:352 msgid "Designar a 1 persona de contacto dedicada del Cliente durante toda la duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:352 +#: ../../content/legal/terms/i18n/enterprise_es.rst:354 msgid "Designar a 1 persona de contacto que se dedique al Cliente a lo largo de la Duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:354 +#: ../../content/legal/terms/i18n/enterprise_es.rst:356 msgid "Notificar por escrito a Odoo SA 30 días antes de cambiar el punto principal de contacto para trabajar con otro Partner de Odoo o directamente con Odoo SA" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:358 +#: ../../content/legal/terms/i18n/enterprise_es.rst:360 msgid "Cuando el Cliente elige usar la Plataforma en la nube, el Cliente acuerda además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:361 +#: ../../content/legal/terms/i18n/enterprise_es.rst:363 msgid "Tomar todas las medidas razonables para mantener sus cuentas de Usuario seguras, incluso al elegir una contraseña segura y no compartirla con nadie más;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:365 +#: ../../content/legal/terms/i18n/enterprise_es.rst:367 msgid "Hacer uso razonable de los servicios de alojamiento, cone xclusiónde cualquier actividad ilegal o actividades abusivas, y observar estrictamente las reglas descritas en la Política de uso aceptable publicada en `acceptable use `__." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:369 +#: ../../content/legal/terms/i18n/enterprise_es.rst:371 msgid "Cuando el Cliente elige la opción de Auto-alojamiento, el Cliente acepta además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:372 +#: ../../content/legal/terms/i18n/enterprise_es.rst:374 msgid "Tomar todas las medidas razonables para proteger los archivos y las bases de datos del Cliente y para garantizar que los datos del Cliente sean seguros y estén protegidos, reconociendo que Odoo SA no se hace responsable de ninguna pérdida de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:376 -msgid "Otorgar a Odoo SA el acceso necesario para verificar la validez de la Edición Enterprise de Odoo uso a solicitud (por ejemplo, si la validación automática no es válida para el Cliente);" +#: ../../content/legal/terms/i18n/enterprise_es.rst:378 +msgid "Otorgar a Odoo SA el acceso necesario para verificar la validez de la Edición Enterprise de Odoo uso a solicitud (por ejemplo, si la validación automática no es válida para el Cliente)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:380 +#: ../../content/legal/terms/i18n/enterprise_es.rst:382 msgid "6.2 No solicitar o contratar" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:381 +#: ../../content/legal/terms/i18n/enterprise_es.rst:384 msgid "Excepto cuando la otra Parte de su consentimiento por escrito, cada una de las Partes, sus filiales y representantes acuerdan no solicitar u ofrecer empleo a ningún empleado de la otra Parte que esté involucrado en la prestación o el uso de los Servicios en virtud de este Acuerdo, durante la vigencia del Acuerdo y por un periodo de 12 meses a partir de la fecha de terminación o vencimiento de este Acuerdo. En caso que ocurra algún incumplimiento de las condiciones de esta sección, se dará por terminado el contrato con el empleado en cuestión y la Parte que ha incumplido esta prohibición acuerda indemnizar a la otra Parte la cifra de treinta mil euros 30.000 EUR (€)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:392 +#: ../../content/legal/terms/i18n/enterprise_es.rst:395 msgid "6.3 Publicidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:394 +#: ../../content/legal/terms/i18n/enterprise_es.rst:397 msgid "Salvo que se notifique lo contrario por escrito, cada Parte otorga a la otra una licencia mundial intransferible, no exclusiva, libre de regalías, para reproducir y mostrar el nombre, logotipos y marcas de la otra Parte, con el único propósito de referirse a la otra Parte como su cliente o proveedor, en sitios web, comunicados de prensa y otros medios de marketing." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:402 +#: ../../content/legal/terms/i18n/enterprise_es.rst:405 msgid "6.4 Confidencialidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:410 +#: ../../content/legal/terms/i18n/enterprise_es.rst:413 msgid "Definición de \"Información confidencial\":" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:405 +#: ../../content/legal/terms/i18n/enterprise_es.rst:408 msgid "Toda la información divulgada por una de las Partes del presente Acuerdo, ya sea oralmente o por escrito, designada como confidencial o razonablemente considerada confidencial dada la naturaleza de la información y las circunstancias de divulgación. En particular, cualquier información relacionada a los negocios, asuntos, productos, desarrollos, secretos comerciales, “know-how”, el personal, los clientes y los proveedores de cualquiera de las Partes del presente Acuerdo, debe ser considerada como confidencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:412 +#: ../../content/legal/terms/i18n/enterprise_es.rst:415 msgid "Para cualquier tipo de información confidencial recibida durante el Plazo de este Acuerdo, la Parte que haya recibido la información confidencial hará uso del mismo grado de precaución que usaría esta Parte para proteger la confidencialidad de información similar que le pertenezca con un grado de precaución razonable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:417 +#: ../../content/legal/terms/i18n/enterprise_es.rst:420 msgid "La Parte que haya recibido la información confidencial puede dar a conocer Información Confidencial de la Parte que haya divulgado dicha información en la medida en que la ley se lo permita. La Parte que haya recibido la información confidencial le dará aviso previo a la Parte que haya divulgado dicha información sobre la información que planea dar a conocer, en la medida en que la ley se lo permita." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:426 +#: ../../content/legal/terms/i18n/enterprise_es.rst:429 msgid "6.5 Protección de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:431 +#: ../../content/legal/terms/i18n/enterprise_es.rst:434 msgid "Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:429 +#: ../../content/legal/terms/i18n/enterprise_es.rst:432 msgid "Los términos “Datos Personales”, “Responsable del tratamiento”, “Tratamiento” tienen los mismos significados que en el Reglamento (UE) 2016/679 y la Directiva 2002/58 / CE, y cualquier reglamento o legislación que los modifique o sustituya (en adelante, “Legislacion de Proteccion de Datos”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:434 +#: ../../content/legal/terms/i18n/enterprise_es.rst:437 msgid "Procesamiento de datos personales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:436 +#: ../../content/legal/terms/i18n/enterprise_es.rst:439 msgid "Las Partes reconocen que la base de datos del Cliente puede contener Datos Personales, de los cuales el Cliente es el Responsable del tratamiento. Esta data será procesada por Odoo SA cuando el Cliente lo indique, al usar cualquiera de los Servicios que requieran una base de datos (por ejemplo, el servicio de hospedaje en la nube o los servicios de actualizaciones), o si el Cliente transfiere su base de datos o una parte de su base de datos a Odoo SA por cualquier motivo relacionado con este Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:443 +#: ../../content/legal/terms/i18n/enterprise_es.rst:446 msgid "Este procesamiento se realizará de conformidad con la legislación de protección de datos. En particular, Odoo SA se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:446 +#: ../../content/legal/terms/i18n/enterprise_es.rst:449 msgid "(a) Solo procesar los datos personales cuando y como lo indique el Cliente, y para elp ropósito de realizar uno de los Servicios en virtud de este Acuerdo, a menos que sea requerido por la ley, en cuyo caso, Odoo SA proporcionará un aviso previo al Cliente, a menos que la ley lo prohíba;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:449 +#: ../../content/legal/terms/i18n/enterprise_es.rst:452 msgid "(b) garantizar que todas las personas dentro de Odoo SA” autorizadas para procesar los Datos personales estén comprometidos con la confidencialidad;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:451 +#: ../../content/legal/terms/i18n/enterprise_es.rst:454 msgid "(c) implementar y mantener medidas técnicas y organizativas adecuadas para proteger los datos personales contra el procesamiento no autorizado o ilegal y contra la pérdida accidental, destrucción, daño, robo, alteración o divulgación;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:454 +#: ../../content/legal/terms/i18n/enterprise_es.rst:457 msgid "(d) enviará sin demora al Cliente cualquier solicitud de protección de datos que se haya enviado a Odoo SA con respecto a la base de datos del Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:456 +#: ../../content/legal/terms/i18n/enterprise_es.rst:459 msgid "(e) notificar al Cliente inmediatamente al momento de conocer y confirmar cualquier accidente, el procesamiento no autorizado o ilegal de, la divulgación o el acceso a los datos personales;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:458 +#: ../../content/legal/terms/i18n/enterprise_es.rst:461 msgid "(f) notificar al Cliente si las instrucciones de procesamiento infringen la Protección de datos aplicables a la legislación, en opinión de Odoo SA;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:460 +#: ../../content/legal/terms/i18n/enterprise_es.rst:463 msgid "(g) poner a disposición del Cliente toda la información necesaria para demostrar el cumplimiento con la legislación de protección de datos, permitir y contribuir razonablemente a las auditorías, incluidas las inspecciones, realizadas o exigidas por el Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:463 +#: ../../content/legal/terms/i18n/enterprise_es.rst:466 msgid "(h) eliminar permanentemente todas las copias de la base de datos del Cliente en posesión de Odoo SA, o devolver dichos datos, a elección del Cliente, a la terminación de este Acuerdo, sujeto a los retrasos especificados en la Política de privacidad de Odoo SA (`Privacy `__)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:468 +#: ../../content/legal/terms/i18n/enterprise_es.rst:471 msgid "En relación a los puntos (d) y (f), el Cliente acepta proporcionar a Odoo SA información de contacto precisa en todo momento, según sea necesario para notificar al responsable de la Legislación de Protección de Datos del Cliente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:473 +#: ../../content/legal/terms/i18n/enterprise_es.rst:476 msgid "Sub procesadores" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:475 +#: ../../content/legal/terms/i18n/enterprise_es.rst:478 msgid "El Cliente reconoce y acepta que, para proporcionar los Servicios, Odoo SA puede utilizar a terceros como proveedores de servicios para procesar Datos Personales (en adelante “Sub-procesadores”). Odoo SA se compromete a utilizar Sub-procesadores únicamente de conformidad con la Legislación de Protección de Datos. Este uso estará amparado bajo un contrato entre Odoo SA y el Sub-procesador que de garantías para estos servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:481 +#: ../../content/legal/terms/i18n/enterprise_es.rst:484 msgid "La Política de privacidad de Odoo SA, publicada en `Odoo Privacy `_ establece información actualizada en relación a los nombres y propósitos de los Sub-procesadores que se encuentran actualmente en uso por Odoo SA para la ejecución de los Servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:488 +#: ../../content/legal/terms/i18n/enterprise_es.rst:491 msgid "6.6 Terminación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:490 +#: ../../content/legal/terms/i18n/enterprise_es.rst:493 msgid "En el supuesto de que alguna de las Partes incumpla con alguna de sus obligaciones establecidas en el presente Acuerdo, y si dicho incumplimiento no ha sido subsanado entre los siguientes 30 días contados a partir de la fecha de notificación escrita de dicho incumplimiento, este Acuerdo se considerará como terminado inmediatamente por la Parte que ha cumplido sus obligaciones." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:495 +#: ../../content/legal/terms/i18n/enterprise_es.rst:498 msgid "De igual manera, Odoo SA puede terminar el Acuerdo inmediatamente si el Cliente no cumple con su obligación de pago del Servicio dentro de los 21 días siguientes a la fecha de la respectiva facturación, y después de haber emitido al menos 3 recordatorios de pago." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:499 +#: ../../content/legal/terms/i18n/enterprise_es.rst:502 msgid "Disposiciones supervivientes: Las secciones \":ref:`confidentiality_es`\", “:ref:`disclaimers_es`\",“:ref:`liability_es`\", y “:ref:`general_provisions_es`” estarán vigentes incluso después de cualquier terminación o vencimiento del presente Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:506 +#: ../../content/legal/terms/i18n/enterprise_es.rst:509 msgid "7 Garantías, Renuncias, Responsabilidad Civil." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:511 +#: ../../content/legal/terms/i18n/enterprise_es.rst:514 msgid "7.1 Garantías" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:513 +#: ../../content/legal/terms/i18n/enterprise_es.rst:516 msgid "Odoo SA posee los derechos de autor o un equivalente [#cla1]_ sobre el 100% del código del Software. Odoo SA confirma que todas las bibliotecas de software necesarias para el uso del Software están disponibles bajo una licencia compatible con la licencia del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:517 +#: ../../content/legal/terms/i18n/enterprise_es.rst:520 msgid "Durante la vigencia del presente Acuerdo, Odoo SA se compromete a emplear esfuerzos comercialmente razonables para ejecutar los Servicios de conformidad con los estándares de la industria generalmente aceptados, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:521 +#: ../../content/legal/terms/i18n/enterprise_es.rst:524 msgid "Los sistemas informáticos del Cliente se encuentren en un buen estado operacional y, para el alojamiento en servidores propios, el Software será instalado en un ambiente adecuado y operativo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:524 +#: ../../content/legal/terms/i18n/enterprise_es.rst:527 msgid "El Cliente brindará información pertinente para la resolución de problemas y, para el alojamiento en servidores propios, cualquier acceso que Odoo SA pueda necesitar para identificar, reproducir y solventar los problemas;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:528 +#: ../../content/legal/terms/i18n/enterprise_es.rst:531 msgid "Todas las cantidades debidas a Odoo SA hayan sido pagadas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:530 +#: ../../content/legal/terms/i18n/enterprise_es.rst:533 msgid "Odoo SA está obligado únicamente a reanudar la ejecución de los Servicios sin cargos adicionales en caso que Odoo SA incumpla alguna de las garantías establecidas. Este será el único y exclusivo recurso que el Cliente podrá usar." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:534 +#: ../../content/legal/terms/i18n/enterprise_es.rst:537 msgid "Contribuciones externas son cubiertas por el Acuerdo de Licencia de Derechos de Autor, el cual provee a Odoo SA una licencia de derechos de autor y de patente permanente, gratis e irrevocable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:538 +#: ../../content/legal/terms/i18n/enterprise_es.rst:541 msgid "Las contribuciones externas están cubiertas por un `acuerdo de licencia de derechos de autor `__, que proporciona una licencia de derechos de autor y patente permanente, gratuita e irrevocable a Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:546 +#: ../../content/legal/terms/i18n/enterprise_es.rst:549 msgid "7.2 Aviso legal" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:548 +#: ../../content/legal/terms/i18n/enterprise_es.rst:551 msgid "Excepto por lo establecido expresamente en este Acuerdo, ninguna de las Partes podrá ofrecer garantías de ningún tipo, ya sean expresas, implícitas, estatutarias o de otro tipo, y cada Parte rechaza cualquier garantía implícita, tal y como garantías de comercialización, idóneas para un propósito especifico o de no cumplimiento, en la medida máxima permitida por la ley aplicable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:553 +#: ../../content/legal/terms/i18n/enterprise_es.rst:556 msgid "Odoo SA no garantiza que el Software cumpla con leyes o regulaciones locales o internacionales." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:558 +#: ../../content/legal/terms/i18n/enterprise_es.rst:561 msgid "7.3 Limitación de responsabilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:560 +#: ../../content/legal/terms/i18n/enterprise_es.rst:563 msgid "De conformidad a la medida máxima permitida por la ley, la responsabilidad agregada de cada una de las Partes junto con sus afiliados que surjan de o estén relacionados con este Acuerdo, no excederá el 50% del monto total pagado por el Cliente en virtud de este Acuerdo durante los 12 meses inmediatamente anteriores a la fecha del evento que da lugar a tal reclamo. Las reclamaciones múltiples no ampliarán esta limitación." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:566 -msgid "En ningún caso, ninguna de las Parte o sus afiliados serán responsables por daños directos, especiales, ejemplares, incidentales o consecuentes de cualquier tipo, incluidos, entre otros, la pérdida de ingresos, ganancias, ahorros, pérdida de negocios u otras pérdidas financieras, costos de inactividad o demora, datos perdidos o dañados, que surjan de o en conexión con este Acuerdo, independientemente de la forma de acción, ya sea en contrato, responsabilidad civil (incluida negligencia estricta) o cualquier otra teoría legal o equitativa, incluso si una de las Partes o sus afiliados han sido informados de la posibilidad de tales daños, o si las medidas de una de las Partes o sus afiliados no cumplen con su propósito esencial." +#: ../../content/legal/terms/i18n/enterprise_es.rst:569 +msgid "En ningún caso, ninguna de las Parte o sus afiliados serán responsables por daños directos, especiales, ejemplares, incidentales o consecuentes de cualquier tipo, incluidos, entre otros, la pérdida de ingresos, ganancias, ahorros, pérdida de negocios u otras pérdidas financieras, costos de inactividad o demora, datos perdidos o dañados, que surjan de o en conexión con este Acuerdo, independientemente de la forma de acción, ya sea en contrato, agravio u otra forma, incluso si una de las Partes o sus afiliados han sido informados de la posibilidad de tales daños, o si el remedio de una de las Partes o sus afiliados no cumplen con su propósito esencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:578 +#: ../../content/legal/terms/i18n/enterprise_es.rst:581 msgid "7.4 Fuerza mayor" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:580 +#: ../../content/legal/terms/i18n/enterprise_es.rst:583 msgid "Ninguna de las Partes será responsable ante la otra Parte por la demora o la falta de cumplimiento de sus obligaciones estipuladas en este Acuerdo cuando tal incumplimiento o retraso sea causado por fuerza mayor, tal y como regulaciones gubernamentales, incendios, huelgas, guerras, inundaciones, accidentes, epidemias, embargos, apropiaciones de instalaciones o productos en su totalidad o en parte por cualquier autoridad gubernamental o pública, o cualquier otra causa o causas, ya sean de naturaleza similares o diferentes, que están más allá del control razonable de dicha parte siempre que tal causa o causas existan efectivamente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:591 +#: ../../content/legal/terms/i18n/enterprise_es.rst:594 msgid "8 Disposiciones generales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:596 +#: ../../content/legal/terms/i18n/enterprise_es.rst:599 msgid "8.1 Ley aplicable" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:598 +#: ../../content/legal/terms/i18n/enterprise_es.rst:601 msgid "Este Acuerdo y todos los pedidos del Cliente estarán sujetos a las leyes del Reino de Bélgica. Cualquier disputa que surja en relación a este Acuerdo o de cualquier pedido del Cliente será sujeta a la jurisdicción exclusiva del Tribunal de Nivelles pertinente para litigar estas disputas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:605 +#: ../../content/legal/terms/i18n/enterprise_es.rst:608 msgid "8.2 Divisibilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:607 +#: ../../content/legal/terms/i18n/enterprise_es.rst:610 msgid "En caso de que una o más de las disposiciones establecidas en este Acuerdo o cualquiera de sus aplicaciones sean inválidas, ilegales o no exigibles en algún aspecto, la validez, legalidad y exigibilidad de las disposiciones restantes del presente Acuerdo y sus aplicaciones no se verán afectadas ni menoscabadas ninguna manera. Ambas Partes se comprometen a reemplazar cualquier provisión inválida, ilegal o inaplicable de este Acuerdo por una provisión válida que tenga el mismo efecto y objetivo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:617 +#: ../../content/legal/terms/i18n/enterprise_es.rst:620 msgid "9 Apéndice A: Licencia de Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:621 +#: ../../content/legal/terms/i18n/enterprise_es.rst:624 msgid "La versión Enterprise de Odoo tiene la licencia Odoo Enterprise Edition v1.0, la cual es definida de la siguiente manera:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:630 +#: ../../content/legal/terms/i18n/enterprise_es.rst:633 msgid "Ver :ref:`odoo_enterprise_license`." msgstr "" @@ -3877,135 +3878,131 @@ msgstr "" msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:11 -msgid "Esta es una traducción al español del \"Odoo Partnership Agreement\". Esta traducción se proporciona con la esperanza de que facilitará la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Partnership Agreement\" es :ref:`la versión original en inglés `." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:29 +#: ../../content/legal/terms/i18n/partnership_es.rst:15 msgid "Versión 11 - 2023-05-19" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:31 +#: ../../content/legal/terms/i18n/partnership_es.rst:17 #: ../../content/legal/terms/i18n/partnership_fr.rst:27 msgid "ENTRE:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:32 +#: ../../content/legal/terms/i18n/partnership_es.rst:18 msgid "Odoo S.A., una empresa que tiene su sede social en Chaussée de Namur, 40, 1367 Grand-Rosière," msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:33 +#: ../../content/legal/terms/i18n/partnership_es.rst:19 msgid "Bélgica, y sus filiales (en adelante denominados conjuntamente “ODOO”)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:34 +#: ../../content/legal/terms/i18n/partnership_es.rst:20 msgid "Y:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:35 +#: ../../content/legal/terms/i18n/partnership_es.rst:21 msgid "_____________________________________________, una empresa que tiene su domicilio social en" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:36 +#: ../../content/legal/terms/i18n/partnership_es.rst:22 #: ../../content/legal/terms/i18n/partnership_fr.rst:32 #: ../../content/legal/terms/partnership.rst:28 msgid "_____________________________________________________________________________________." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:37 +#: ../../content/legal/terms/i18n/partnership_es.rst:23 msgid "(en adelante denominado “EL COLABORADOR”)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:39 +#: ../../content/legal/terms/i18n/partnership_es.rst:25 msgid "ODOO y EL COLABORADOR se denominan individualmente “Parte” y conjuntamente “las Partes”." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:42 +#: ../../content/legal/terms/i18n/partnership_es.rst:28 msgid "1 Objeto" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:43 +#: ../../content/legal/terms/i18n/partnership_es.rst:30 msgid "El presente Contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios a EL COLABORADOR, acceso al software Odoo Enterprise Edition, y bajo las cuales EL COLABORADOR cumple con las obligaciones establecidas a continuación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:47 +#: ../../content/legal/terms/i18n/partnership_es.rst:34 msgid "Por la presente ODOO nombra a EL COLABORADOR, y EL COLABORADOR acepta ser nombrado, socio no exclusivo para promover y vender “Odoo Enterprise Edition” a los clientes." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:50 +#: ../../content/legal/terms/i18n/partnership_es.rst:37 msgid "EL COLABORADOR se compromete a hacer su mejor esfuerzo para vender contratos de Odoo Enterprise a sus clientes. En apoyo a esta afirmación, EL COLABORADOR dará prioridad a la comercialización de la versión “Odoo Enterprise Edition” a clientes potenciales y clientes. EL COLABORADOR siempre tiene la posibilidad de vender servicios con otras versiones del software, como “Odoo Community Edition”, en caso de ser necesario." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:57 +#: ../../content/legal/terms/i18n/partnership_es.rst:44 msgid "2 Duración del Contrato" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:58 +#: ../../content/legal/terms/i18n/partnership_es.rst:46 msgid "La duración de este contrato será de un año (\"la Duración\") a partir de la fecha de la firma. Se renueva automáticamente por una duración igual, a menos que cualquiera de las partes notifique por escrito a la otra parte su terminación como mínimo 30 días antes del final de la duración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:63 +#: ../../content/legal/terms/i18n/partnership_es.rst:51 msgid "3 Acceso a Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:66 +#: ../../content/legal/terms/i18n/partnership_es.rst:54 msgid "3.1 Acceso a la plataforma del proyecto" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:67 +#: ../../content/legal/terms/i18n/partnership_es.rst:56 msgid "Para ayudar a EL COLABORADOR a promover Odoo Enterprise Edition, ODOO otorga a EL COLABORADOR acceso a su repositorio de código del proyecto para todas las “Aplicaciones Odoo Enterprise Edition”, en los términos establecidos en :ref:`appendix_p_a_es` y las condiciones restringidas del presente Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:72 +#: ../../content/legal/terms/i18n/partnership_es.rst:61 msgid "Además, ODOO otorga a EL COLABORADOR acceso gratuito a la plataforma ODOO.SH con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:75 +#: ../../content/legal/terms/i18n/partnership_es.rst:64 msgid "EL COLABORADOR no tiene permitido bloquear, restringir o limitar de ninguna manera el acceso y uso de la Licencia Odoo Enterprise Edition por parte del cliente, sin consulta previa y autorización por escrito de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:82 +#: ../../content/legal/terms/i18n/partnership_es.rst:71 msgid "3.2 Restricciones" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:83 +#: ../../content/legal/terms/i18n/partnership_es.rst:73 msgid "EL COLABORADOR se compromete a mantener la confidencialidad del código fuente de las aplicaciones Odoo Enterprise Edition entre su personal. El acceso al código fuente de Odoo Enterprise Edition para los clientes se rige por el Contrato de suscripción de Odoo Enterprise. EL COLABORADOR se compromete a NO redistribuir este código a terceros sin el permiso por escrito de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:89 +#: ../../content/legal/terms/i18n/partnership_es.rst:79 msgid "PARTNER se compromete a no ofrecer servicios en Odoo Enterprise Edition a clientes que no estén cubiertos por una suscripción de Odoo Enterprise, incluso durante la fase de implementación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:92 +#: ../../content/legal/terms/i18n/partnership_es.rst:82 msgid "A pesar de lo anterior, EL COLABORADOR se compromete a preservar por completo la integridad del código de Odoo Enterprise Edition necesario para verificar la validez del uso de Odoo Enterprise Edition y para recopilar estadísticas necesarias para este fin." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:98 +#: ../../content/legal/terms/i18n/partnership_es.rst:88 msgid "4 Servicios de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:101 +#: ../../content/legal/terms/i18n/partnership_es.rst:91 msgid "4.1 Niveles de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:102 +#: ../../content/legal/terms/i18n/partnership_es.rst:93 msgid "El programa de socios de Odoo consta de dos tipos de asociaciones y cuatro niveles; \"Learning Partners\" es para empresas que desean todo lo necesario para comenzar a implementar Odoo, sin visibilidad como socio oficial hasta que obtengan la experiencia requerida; \"Official Partners\" es para empresas que desean la visibilidad como Ready, Silver y Gold, según su experiencia con Odoo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 +#: ../../content/legal/terms/i18n/partnership_es.rst:99 msgid "El nivel de colaboración otorgado a EL COLABORADOR depende de los *nuevos usuarios netos de Odoo Enterprise vendidos* en los últimos 12 meses, el número de recursos certificados y la Tasa de Retención de clientes. Los *nuevos usuarios netos de Odoo Enterprise vendidos* incluyen nuevos clientes, ventas adicionales a clientes existentes, reducciones en ventas a clientes existentes y la pérdida de clientes. Las renovaciones de contratos existentes no se cuentan como parte del número de usuarios vendidos, pero EL COLABORADOR aún recibe una comisión por estos contratos según se establece en la sección :ref:`benefits_es`." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:117 +#: ../../content/legal/terms/i18n/partnership_es.rst:108 msgid "La tabla siguiente resume los requisitos para cada nivel de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:119 +#: ../../content/legal/terms/i18n/partnership_es.rst:110 msgid "La *Tasa de Retención* de clientes se calcula dividiendo el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años que están actualmente activos, entre el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4013,8 +4010,8 @@ msgstr "" msgid "Learning Partner" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4022,8 +4019,8 @@ msgstr "" msgid "Official: Ready" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4031,8 +4028,8 @@ msgstr "" msgid "Official: Silver" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4040,12 +4037,12 @@ msgstr "" msgid "Official: Gold" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 msgid "Nuevos Usuarios netos de Odoo Enterprise vendidos anualmente" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:114 @@ -4053,175 +4050,175 @@ msgstr "" msgid "0" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/partnership.rst:114 msgid "10" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 msgid "50" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/partnership.rst:114 msgid "300" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 msgid "Número de empleados certificados en al menos uno de las 3 últimas versiones de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "1" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "3" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "6" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 msgid "Tasa de Retención mínima" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "n/a" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "70%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "80%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:135 +#: ../../content/legal/terms/i18n/partnership_es.rst:126 msgid "Las certificaciones son personales, por lo que cuando un miembro certificado del personal deja la empresa, EL COLABORADOR debe notificarlo a ODOO para que actualice la cantidad de recursos certificados activos para el contrato de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:139 +#: ../../content/legal/terms/i18n/partnership_es.rst:130 msgid "ODOO revisará trimestralmente el nivel de colaboración de EL COLABORADOR y lo ajustará al nivel más alto para el cual se cumplan los 3 requisitos." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:142 +#: ../../content/legal/terms/i18n/partnership_es.rst:133 msgid "Sin embargo, los \"Official Partners\" pueden actualizarse automáticamente a un nivel superior una vez que alcancen los 3 requisitos para ese nivel de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 +#: ../../content/legal/terms/i18n/partnership_es.rst:139 msgid "4.2 Ventajas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:150 +#: ../../content/legal/terms/i18n/partnership_es.rst:141 msgid "En la tabla siguiente se describen los detalles de las ventajas para cada nivel de colaboración:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:159 +#: ../../content/legal/terms/i18n/partnership_es.rst:150 msgid "**Reconocimiento**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 msgid "Visibilidad en odoo.com" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:190 -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 #: ../../content/legal/terms/partnership.rst:148 #: ../../content/legal/terms/partnership.rst:178 #: ../../content/legal/terms/partnership.rst:185 msgid "No" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Ready Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Silver Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Gold Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:154 msgid "Derechos de uso de la marca registrada “Odoo” y logotipos" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:154 +#: ../../content/legal/terms/i18n/partnership_es.rst:159 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:165 #: ../../content/legal/terms/i18n/partnership_es.rst:168 -#: ../../content/legal/terms/i18n/partnership_es.rst:170 -#: ../../content/legal/terms/i18n/partnership_es.rst:174 -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:180 -#: ../../content/legal/terms/i18n/partnership_es.rst:190 -#: ../../content/legal/terms/i18n/partnership_es.rst:195 -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:171 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 +#: ../../content/legal/terms/i18n/partnership_es.rst:186 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 msgid "Sí" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:166 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 msgid "**Ventajas de la formación**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:168 +#: ../../content/legal/terms/i18n/partnership_es.rst:159 msgid "Coaching de ventas y webinars" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:170 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 msgid "Acceso a la base de conocimiento Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:172 +#: ../../content/legal/terms/i18n/partnership_es.rst:163 msgid "**Ventajas del software**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:174 +#: ../../content/legal/terms/i18n/partnership_es.rst:165 msgid "Acceso al código fuente de Odoo Enterprise y repositorio Github" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:177 +#: ../../content/legal/terms/i18n/partnership_es.rst:168 msgid "Código de extensión de prueba de Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:180 +#: ../../content/legal/terms/i18n/partnership_es.rst:171 msgid "Acceso a Odoo.sh con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:183 +#: ../../content/legal/terms/i18n/partnership_es.rst:174 msgid "**Ventajas de las ventas**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 msgid "Comisión por la plataforma Odoo SH [#s1]_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:171 @@ -4229,189 +4226,189 @@ msgstr "" msgid "10%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 #: ../../content/legal/terms/i18n/partnership_fr.rst:179 #: ../../content/legal/terms/partnership.rst:171 msgid "50%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 msgid "Comisión por Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:173 msgid "15%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:173 msgid "20%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:190 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 msgid "Acceso a un gestor de cuentas especializado y Partner Dashboard" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:193 +#: ../../content/legal/terms/i18n/partnership_es.rst:184 msgid "**Ventajas de marketing**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:195 +#: ../../content/legal/terms/i18n/partnership_es.rst:186 msgid "Material de marketing" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 msgid "Evento de EL COLABORADOR - Asistencia y promoción de ODOO" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:201 +#: ../../content/legal/terms/i18n/partnership_es.rst:192 msgid "hasta un máximo de 150€ (o $180) de comisión mensual por suscripción, o 1440€ (o $1728) de comisión anual por suscripción." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:205 +#: ../../content/legal/terms/i18n/partnership_es.rst:196 msgid "4.3 Reconocimiento de socios" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:206 +#: ../../content/legal/terms/i18n/partnership_es.rst:198 msgid "ODOO promocionará EL COLABORADOR como socio oficial en el sitio web oficial (odoo.com)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:208 +#: ../../content/legal/terms/i18n/partnership_es.rst:200 msgid "ODOO concede a EL COLABORADOR, de forma no exclusiva, el derecho a usar y reproducir el logotipo de socio de ODOO del nivel de colaboración correspondiente y el nombre “Odoo” en relación con este contrato de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:212 +#: ../../content/legal/terms/i18n/partnership_es.rst:204 msgid "Cada Parte se compromete a respetar todos los derechos de la otra Parte en todos los elementos mencionados en el párrafo anterior y, más concretamente, cada Parte debe abstenerse de causar cualquier analogía o crear confusión entre sus respectivas compañías en el público general, por cualquier motivo y por cualquier medio." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:218 +#: ../../content/legal/terms/i18n/partnership_es.rst:210 msgid "4.4 Ventajas de la formación" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:219 +#: ../../content/legal/terms/i18n/partnership_es.rst:212 msgid "EL COLABORADOR tiene acceso a la base de conocimiento de ODOO durante la duración de este Contrato. La base de conocimiento de ODOO es una plataforma electrónica en línea que contiene un conjunto de documentos comerciales, funcionales y de marketing para ayudar a EL COLABORADOR a adquirir y aprovechar el conocimiento de Odoo, hacer crecer su negocio, atraer más clientes y crear conciencia de marca." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:225 +#: ../../content/legal/terms/i18n/partnership_es.rst:218 msgid "EL COLABORADOR podrá acceder al coaching comercial facilitado por su gestor de cuentas especializado, designado por ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:228 +#: ../../content/legal/terms/i18n/partnership_es.rst:221 msgid "EL COLABORADOR también tiene la opción de comprar servicios de soporte o de formación suscribiéndose a un Success Pack de Odoo, por una tarifa adicional." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:232 +#: ../../content/legal/terms/i18n/partnership_es.rst:225 msgid "4.5 Comisiones por los servicios de Odoo vendidos por EL COLABORADOR" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:233 +#: ../../content/legal/terms/i18n/partnership_es.rst:227 msgid "Para los servicios ODOO comprados por un cliente a través de EL COLABORADOR, y siempre que el PARTNER mantenga una relación contractual con el cliente correspondiente, EL COLABORADOR ecibirá una comisión de acuerdo con la tabla de la sección :ref:`benefits_es` y su nivel de asociación en la fecha de la factura del cliente." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:240 +#: ../../content/legal/terms/i18n/partnership_es.rst:234 msgid "5 Tarifas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:241 +#: ../../content/legal/terms/i18n/partnership_es.rst:236 msgid "EL COLABORADOR se compromete a pagar la tarifa de la colaboración al recibir la factura anual enviada por ODOO. La tarifa se especificará por escrito al momento de la firma de este contracto." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:244 +#: ../../content/legal/terms/i18n/partnership_es.rst:239 msgid "EL COLABORADOR reconoce que la tarifa de colaboración mencionadas anteriormente no son reembolsables." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:246 +#: ../../content/legal/terms/i18n/partnership_es.rst:241 msgid "Todos los honorarios y cargos son exclusivos de todos los impuestos, tarifas o cargos gubernamentales, federales, provinciales, estatales, locales u otros aplicables (en conjunto, \"Impuestos\"). EL COLABORADOR es responsable de pagar todos los Impuestos asociados a las compras realizadas por EL COLABORADOR bajo este Contrato, excepto cuando ODOO esté legalmente obligado a pagar o recaudar Impuestos de los cuales EL COLABORADOR es responsable." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:253 +#: ../../content/legal/terms/i18n/partnership_es.rst:248 msgid "6 Resolución" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:254 +#: ../../content/legal/terms/i18n/partnership_es.rst:250 msgid "En el caso de que cualquiera de las Partes no cumpla con cualquiera de sus obligaciones que se derivan de este documento, y si tal incumplimiento no se ha rectificado en un período de 30 días naturales a partir de la notificación por escrito de dicho incumplimiento, la Parte que no incumplió sus obligaciones puede rescindir este contrato inmediatamente." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:261 +#: ../../content/legal/terms/i18n/partnership_es.rst:257 msgid "Disposiciones subsistentes:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:260 +#: ../../content/legal/terms/i18n/partnership_es.rst:256 msgid "Las secciones « :ref:`restrictions_es` », « :ref:`p_liability_es` », y « :ref:`gov_law_es` » mantendrán su vigencia tras cualquier resolución o expiración de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:264 +#: ../../content/legal/terms/i18n/partnership_es.rst:260 msgid "6.1 Consecuencia de la resolución" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:269 +#: ../../content/legal/terms/i18n/partnership_es.rst:266 msgid "En el momento de la resolución de este contrato, EL COLABORADOR:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:266 +#: ../../content/legal/terms/i18n/partnership_es.rst:263 msgid "no deberá utilizar más los materiales y/o la marca Odoo ni reclamar la existencia de ninguna colaboración o relación con ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:268 +#: ../../content/legal/terms/i18n/partnership_es.rst:265 msgid "deberá cumplir con sus obligaciones durante cualquier período de aviso previo a dicha resolución;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:269 +#: ../../content/legal/terms/i18n/partnership_es.rst:266 msgid "ya no podrá usar Odoo Enterprise para fines de desarrollo, prueba o producción" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:274 +#: ../../content/legal/terms/i18n/partnership_es.rst:271 msgid "7 Responsabilidad e indemnizaciones" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:275 +#: ../../content/legal/terms/i18n/partnership_es.rst:273 msgid "Ambas Partes están vinculadas por una obligación de medios aquí descrita." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:277 +#: ../../content/legal/terms/i18n/partnership_es.rst:275 msgid "En la medida máxima permitida por la ley, la responsabilidad de cada Parte por cualquier reclamo, pérdida, daño o gasto derivado de cualquier manera o bajo cualquier circunstancia del presente contrato se limitará a los daños directos demostrados, pero en ningún caso excederá por todos los eventos o series de eventos relacionados que ocasionen daños la cantidad total de las tarifas pagadas por EL COLABORADOR en el transcurso de los seis (6) meses inmediatamente anteriores a la fecha del evento que dio lugar a dicha reclamación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:284 +#: ../../content/legal/terms/i18n/partnership_es.rst:282 msgid "En ningún caso cada Parte será responsable de ningún daño indirecto o consecuente, incluyendo, entre otros, pero no limitándose a, reclamaciones de clientes o terceros, pérdidas de ingresos, ganancias, ahorros, pérdidas de negocios y otras pérdidas financieras, costos de paralización y retraso, datos perdidos o dañados derivados o relacionados con el cumplimiento de sus obligaciones en virtud de este Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:290 +#: ../../content/legal/terms/i18n/partnership_es.rst:288 msgid "EL COLABORADOR reconoce que no tiene ninguna expectativa y que no ha recibido garantías de recuperar ninguna inversión realizada en la ejecución de este contrato y el programa de socios de Odoo o de obtener ninguna cantidad anticipada de ganancias en virtud de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:296 +#: ../../content/legal/terms/i18n/partnership_es.rst:294 msgid "8 Imagen de marca" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:297 +#: ../../content/legal/terms/i18n/partnership_es.rst:296 msgid "La marca \"Odoo\" (incluida la palabra y sus representaciones visuales y logotipos) es exclusiva propiedad de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:300 +#: ../../content/legal/terms/i18n/partnership_es.rst:299 msgid "ODOO autoriza a PARTNER a usar la marca \"Odoo\" para promocionar sus productos y servicios, solo por la Duración del Contrato, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:303 +#: ../../content/legal/terms/i18n/partnership_es.rst:302 msgid "no hay confusión posible de que el servicio sea proporcionado por PARTNER, no por ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:304 +#: ../../content/legal/terms/i18n/partnership_es.rst:303 msgid "PARTNER no use la palabra \"Odoo\" en el nombre de su compañía, nombre de producto, nombre de dominio y no registrar ninguna marca que la incluya." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:307 +#: ../../content/legal/terms/i18n/partnership_es.rst:306 msgid "Ambas Partes se abstendrán de dañar de ninguna manera la imagen de marca y la reputación de la otra Parte en el cumplimiento de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:310 +#: ../../content/legal/terms/i18n/partnership_es.rst:309 msgid "El incumplimiento de las disposiciones de esta sección será causa de resolución de este Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:314 +#: ../../content/legal/terms/i18n/partnership_es.rst:313 msgid "8.1 Publicidad" msgstr "" @@ -4423,44 +4420,44 @@ msgstr "" msgid "8.2 No captación o contratación" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:324 +#: ../../content/legal/terms/i18n/partnership_es.rst:325 msgid "Excepto cuando la otra Parte dé su consentimiento por escrito, cada Parte, sus afiliados y representantes acuerdan no captar u ofrecer empleo a ningún empleado de la otra Parte que participe en la realización o uso de los servicios de este contrato, durante la duración de este contrato y por un período de 24 meses a partir de la fecha de resolución o expiración de este contrato. En caso de cualquier incumplimiento de las condiciones de esta sección que conduzca al despido de dicho empleado con este objetivo, la Parte incumplidora se compromete a pagar a la otra parte la cantidad de 30 000,00 EUR (€) (treinta mil euros)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:335 +#: ../../content/legal/terms/i18n/partnership_es.rst:336 msgid "8.3 Contratistas independientes" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:336 +#: ../../content/legal/terms/i18n/partnership_es.rst:338 msgid "Las Partes son contratistas independientes, y este contrato no debe interpretarse como la configuración de cualquier Parte como socia, empresa conjunta o fiduciaria de la otra, como la creación de otra forma de asociación legal que exigiría responsabilidad a una Parte por la acción o la falta de acción de la otra, o como la prestación a cada Parte del derecho, poder o autoridad (expresa o implícita) para crear cualquier deber u obligación de la otra." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:346 +#: ../../content/legal/terms/i18n/partnership_es.rst:348 msgid "9 Ley y jurisdicción aplicables" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:347 +#: ../../content/legal/terms/i18n/partnership_es.rst:350 msgid "Este contrato se rige y se interpreta de acuerdo con las leyes de Bélgica. Todas las disputas que surjan en relación con este contrato para las que no se pueda encontrar una solución amistosa serán resueltas definitivamente en los Tribunales de Bélgica en Nivelles." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:-1 -#: ../../content/legal/terms/i18n/partnership_es.rst:367 +#: ../../content/legal/terms/i18n/partnership_es.rst:370 msgid "Firmas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:369 +#: ../../content/legal/terms/i18n/partnership_es.rst:372 msgid "Por ODOO," msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:369 +#: ../../content/legal/terms/i18n/partnership_es.rst:372 msgid "Por EL COLABORADOR" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:377 +#: ../../content/legal/terms/i18n/partnership_es.rst:380 msgid "|vnegspace| |hspace| Por ODOO, |hspace| Por EL COLABORADOR, |vspace|" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:385 +#: ../../content/legal/terms/i18n/partnership_es.rst:388 msgid "10 Anexo A: Licencia Odoo Enterprise Edition" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index f005b25f22..ea40f376dc 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index d2dfdbbf66..9f90414fca 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -5989,22 +5989,22 @@ msgid "Type `/` in the editor box to structure and format your content. You can msgstr "" #: ../../content/applications/productivity/to_do.rst:23 -msgid "You can create a new to-do on the fly from anywhere in Odoo by clicking the clock button and then :guilabel:`Add a To-Do`." +msgid "You can create a new to-do on the fly from anywhere in Odoo by opening the **command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking :guilabel:`Add a To-Do`, or by clicking the clock button and then :guilabel:`Add a To-Do`." msgstr "" #: ../../content/applications/productivity/to_do.rst:0 msgid "Adding a to-do on the fly" msgstr "" -#: ../../content/applications/productivity/to_do.rst:30 +#: ../../content/applications/productivity/to_do.rst:31 msgid "Converting to-dos into project tasks" msgstr "" -#: ../../content/applications/productivity/to_do.rst:32 +#: ../../content/applications/productivity/to_do.rst:33 msgid "If you use the :doc:`Project app <../services/project>`, you can convert to-dos into project tasks. To do so, open a to-do and click the gear button (:guilabel:`⚙`), then :guilabel:`Convert to Task`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:35 +#: ../../content/applications/productivity/to_do.rst:36 msgid "Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and :guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a project task and appears in the selected project." msgstr "" @@ -6012,11 +6012,11 @@ msgstr "" msgid "Converting a to-do into a task" msgstr "" -#: ../../content/applications/productivity/to_do.rst:42 +#: ../../content/applications/productivity/to_do.rst:43 msgid "Managing the to-do pipeline" msgstr "" -#: ../../content/applications/productivity/to_do.rst:44 +#: ../../content/applications/productivity/to_do.rst:45 msgid "Your assigned **to-dos** are displayed on the app dashboard. You can drag and drop a to-do to move it from one stage to another." msgstr "" @@ -6024,11 +6024,11 @@ msgstr "" msgid "Example of a to-do pipeline" msgstr "" -#: ../../content/applications/productivity/to_do.rst:51 +#: ../../content/applications/productivity/to_do.rst:52 msgid "Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to create a new stage." msgstr "" -#: ../../content/applications/productivity/to_do.rst:53 +#: ../../content/applications/productivity/to_do.rst:54 msgid "Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, :guilabel:`Edit`, or :guilabel:`Delete` it." msgstr "" @@ -6036,11 +6036,11 @@ msgstr "" msgid "Stage settings button" msgstr "" -#: ../../content/applications/productivity/to_do.rst:60 +#: ../../content/applications/productivity/to_do.rst:61 msgid "Scheduling activities" msgstr "" -#: ../../content/applications/productivity/to_do.rst:62 +#: ../../content/applications/productivity/to_do.rst:63 msgid "To schedule an activity on a to-do, click the clock button on the app dashboard, then the :guilabel:`+ Schedule an activity` button." msgstr "" @@ -6048,39 +6048,39 @@ msgstr "" msgid "Scheduling an activity from the To-do dashboard" msgstr "" -#: ../../content/applications/productivity/to_do.rst:68 +#: ../../content/applications/productivity/to_do.rst:69 msgid "To create the activity:" msgstr "" -#: ../../content/applications/productivity/to_do.rst:70 +#: ../../content/applications/productivity/to_do.rst:71 msgid "Select an :guilabel:`Activity Type`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:71 +#: ../../content/applications/productivity/to_do.rst:72 msgid "Select a :guilabel:`Due date`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:72 +#: ../../content/applications/productivity/to_do.rst:73 msgid "Choose who the activity should be :guilabel:`Assigned to`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:73 +#: ../../content/applications/productivity/to_do.rst:74 msgid "Add a brief :guilabel:`Summary` if needed. You can add a more elaborate description in the :guilabel:`Log a note` box." msgstr "" -#: ../../content/applications/productivity/to_do.rst:76 +#: ../../content/applications/productivity/to_do.rst:77 msgid "Click :guilabel:`Schedule` to complete the action." msgstr "" -#: ../../content/applications/productivity/to_do.rst:79 +#: ../../content/applications/productivity/to_do.rst:80 msgid "The :guilabel:`To Do` activity is *not* a to-do task. Selecting it does not create a to-do task." msgstr "" -#: ../../content/applications/productivity/to_do.rst:82 +#: ../../content/applications/productivity/to_do.rst:83 msgid "Viewing to-dos in the Project app" msgstr "" -#: ../../content/applications/productivity/to_do.rst:84 +#: ../../content/applications/productivity/to_do.rst:85 msgid "If you use the :doc:`Project app <../services/project>`, your to-dos also appear as private tasks under the :guilabel:`My Tasks` view." msgstr "" @@ -6088,7 +6088,7 @@ msgstr "" msgid "Example of a \"My Tasks\" pipeline in the Project app" msgstr "" -#: ../../content/applications/productivity/to_do.rst:91 +#: ../../content/applications/productivity/to_do.rst:92 msgid "A padlock icon is visible on your private tasks to quickly identify them among your project tasks." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 732e4d3918..650e6ab48a 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -42,14 +42,10 @@ msgid "Convert leads into opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 -msgid "The system can generate leads instead of opportunities, in order to add a qualification step before converting a *Lead* into an *Opportunity* and assigning to the right sales people." +msgid "*Leads* act as qualifying steps before an opportunity is created. This provides additional time before a potential opportunity is assigned to a sales person." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 -msgid "You can activate this mode from the CRM Settings. It applies to all your sales channels by default. But you can make it specific for specific channels from their configuration form." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:14 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 #: ../../content/applications/sales/crm/optimize/gamification.rst:11 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 @@ -74,59 +70,133 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 -#: ../../content/applications/sales/rental.rst:20 #: ../../content/applications/sales/sales/invoicing/proforma.rst:14 -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:34 #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:24 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 #: ../../content/applications/sales/subscriptions/closing.rst:31 -#: ../../content/applications/sales/subscriptions/upselling.rst:25 msgid "Configuration" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:16 -msgid "For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings` and activate the *Leads* feature." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:11 +msgid "To activate the *Leads* setting, navigate to :menuselection:`CRM app --> Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Leads setting on CRM configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:18 +msgid "Activating this feature adds a new menu, :guilabel:`Leads`, to the header menu bar at the top of the screen." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Leads menu on CRM application." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:22 -msgid "You will now have a new submenu *Leads* under *Leads* where they will aggregate." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:25 +msgid "Once the *Leads* setting has been activated, it applies to all sales teams by default. To turn off leads for a specific team, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a team from the list to open the record, and uncheck the :guilabel:`Leads` box. Once done, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:29 +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35 msgid "Convert a lead into an opportunity" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:31 -msgid "When you click on a *Lead* you will have the option to convert it to an opportunity and decide if it should still be assigned to the same channel/person and if you need to create a new customer." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:37 +msgid "To convert a lead into an *opportunity*, navigate to :menuselection:`CRM --> Leads`, and click on a :guilabel:`Lead` from the list to open it." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 -msgid "If you already have an opportunity with that customer Odoo will automatically offer you to merge with that opportunity. In the same manner, Odoo will automatically offer you to link to an existing customer if that customer already exists." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:40 +msgid "In the upper-left corner of the screen, click the :guilabel:`Convert to Opportunity` button, which opens a :guilabel:`Convert to opportunity` pop-up window." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:44 -msgid "Merge opportunities" +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Create opportunity button on a lead record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:46 -msgid "Odoo will also automatically propose to merge opportunities if they have the same email address. When merging opportunities, Odoo merges the information into the opportunity which was created first, giving priority to the information present on the first opportunity." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:47 +msgid "On the :guilabel:`Convert to opportunity` pop-up window, in the :guilabel:`Conversion action` field, select the :guilabel:`Convert to opportunity` option." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 -msgid "No information is lost: data from the other opportunity is logged in the chatter and the information fields for easy access." +msgid "If a lead, or an opportunity, already exists in the database for this customer, Odoo automatically suggests merging both leads/opportunities. For more information on merging leads and opportunities, see the section on how to :ref:`merge leads ` below." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:56 +msgid "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which the opportunity should be assigned." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59 +msgid "If the lead has already been assigned to a salesperson or a team, these fields automatically populate with that information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Create opportunity pop-up." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:66 +msgid "Under the :guilabel:`Customer` heading, choose from the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:68 +msgid ":guilabel:`Create a new customer`: Choose this option to use the information in the lead to create a new customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:70 +msgid ":guilabel:`Link to an existing customer`: Choose this option, then select a customer from the resulting drop-down menu, to link this opportunity to the existing customer record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:72 +msgid ":guilabel:`Do not link to a customer`: Choose this option to convert the lead, but not link it to a new or existing customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:75 +msgid "Lastly, when all configurations are complete, click :guilabel:`Create Opportunity`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:80 +msgid "Merge leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:82 +msgid "Odoo automatically detects similar leads and opportunities by comparing the email addresses of the associated contacts. If a similar lead/opportunity is found, a :guilabel:`Similar Lead` smart button appears at the top of the lead/opportunity record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Similar leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:90 +msgid "To compare the details of the similar leads/opportunities, click the :guilabel:`Similar Leads` button. This opens a kanban view with only the similar leads/opportunities. Click into each card to view the details for each lead/opportunity, and confirm if they should be merged." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:57 -msgid "Would you find a duplicate yourself, ...you can also merge opportunities or leads even if the system doesn't propose it." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 +msgid "When merging, Odoo gives priority to whichever lead/opportunity was created in the system first, merging the information into the first created lead/opportunity. However, if a lead and an opportunity are being merged, the resulting record is referred to as an opportunity, regardless of which record was created first." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 -msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:100 +msgid "After confirming that the leads/opportunities should be merged, return to the kanban view using breadcrumbs, or by clicking the :guilabel:`Similar Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to change to list view." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:67 -msgid "It is also possible to merge more than 2 opportunities or leads." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:104 +msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :guilabel:`Action ⚙️ (gear)` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities (or leads)." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:108 +msgid "When :guilabel:`Merge` is selected from the :guilabel:`Action ⚙️ (gear)` drop-down menu, a :guilabel:`Merge` pop-up window appears. In that pop-up window, decide to :guilabel:`Assign opportunities to` a :guilabel:`Salesperson` and/or :guilabel:`Sales Team`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:112 +msgid "Below those fields, the leads/opportunities to merge are listed, along with their related information. To merge those selected leads/opportunities, click :guilabel:`Merge`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:116 +msgid "When merging opportunities, no information is lost. Data from the other opportunity is logged in the chatter, and the information fields, for reference." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Merge option from action menu in list view." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 @@ -335,6 +405,7 @@ msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 +#: ../../content/applications/sales/rental.rst:88 msgid "Pricing" msgstr "" @@ -4916,11 +4987,11 @@ msgid "Rental" msgstr "" #: ../../content/applications/sales/rental.rst:5 -msgid "**Odoo Rental** is a comprehensive solution to manage your rentals." +msgid "The Odoo *Rental* application provides comprehensive solutions to configure and manage rentals." msgstr "" #: ../../content/applications/sales/rental.rst:7 -msgid "From a single view, you can send out quotations, confirm orders, schedule rentals, register when products are picked up and returned, and invoice your customers." +msgid "Send quotations, confirm orders, schedule rentals, register products when they are picked up and returned, and invoice customers from this single platform." msgstr "" #: ../../content/applications/sales/rental.rst:11 @@ -4932,103 +5003,342 @@ msgid "`Odoo Tutorials: Rental `_" msgstr "" #: ../../content/applications/sales/rental.rst:17 -msgid "Rental Pricing" +msgid "Dashboard" msgstr "" -#: ../../content/applications/sales/rental.rst:22 -msgid "Go to :menuselection:`Rental --> Products`, select or create a product, and click on the product's *Rental* tab. Under *Rental Pricing*, click on *Add a price*. Then choose a *Unit* of time (hours, days, weeks, or months), a *Duration*, and a *Price*. You can add as many price lines as necessary, usually to give out discounts for longer rental durations." +#: ../../content/applications/sales/rental.rst:19 +msgid "Upon opening the *Rental* application, the :guilabel:`Rental Orders` dashboard is revealed." msgstr "" #: ../../content/applications/sales/rental.rst:-1 -msgid "Example of rental pricing configuration in Odoo Rental" +msgid "Example of the Rental Orders dashboard available in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:25 +msgid "In the default kanban view, all rentals are visible. Each rental card displays the customer name, the price of the rental, the related sales order number, along with the status of the rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:29 +msgid "Rental kanban cards that do **not** display a rental status means those rentals have confirmed quotations, but have not been picked up yet." msgstr "" #: ../../content/applications/sales/rental.rst:32 -msgid "Under *Reservations*, you can add fines for any *Extra Hour* or *Extra Day*. You can also set a *Security Time*, expressed in hours, to make the product temporarily unavailable between two rental orders." +msgid "On the left sidebar, the :guilabel:`Rental Status` for each rental can be found. Beneath that, the :guilabel:`Invoice Status` of the rentals is accessible. Clicking any option in the left sidebar filters the displayed rentals on the dashboard." msgstr "" #: ../../content/applications/sales/rental.rst:37 -msgid "If you want to rent a product created outside of the Rental app, do not forget to tick *Can be Rented* under the product's name. By default, this option is ticked when you create a product directly from the Rental app." +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 +msgid "Settings" msgstr "" -#: ../../content/applications/sales/rental.rst:42 -msgid "Computing" +#: ../../content/applications/sales/rental.rst:39 +msgid "To configure additional rental delay costs, availability of rental items, or minimum time of rental, navigate to :menuselection:`Rental app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/sales/rental.rst:44 -msgid "Odoo always uses two rules to compute the price of a product when you create a rental order:" +#: ../../content/applications/sales/rental.rst:-1 +msgid "How the Settings page appears in the Odoo Rental application." msgstr "" #: ../../content/applications/sales/rental.rst:46 +msgid "In the :guilabel:`Rental` section, there are options to configure :guilabel:`Default Delay Costs` and :guilabel:`Default Padding Time`. There is also the option to activate :guilabel:`Rental Transfers` and :guilabel:`Digital Documents`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:50 +msgid ":guilabel:`Default Delay Costs` are additional costs for late returns." +msgstr "" + +#: ../../content/applications/sales/rental.rst:51 +msgid ":guilabel:`Default Padding Time` represents the minimum amount of time between two rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:52 +msgid ":guilabel:`Rental Transfers` means stock deliveries and receipts can be used for rental orders." +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid ":guilabel:`Digital Documents` allows users to upload documents for customers to sign prior to" +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "confirming their rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:56 +msgid "In the :guilabel:`Rent Online` section, there are options to configure a :guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability days`, or days during which pickup and return are not possible." +msgstr "" + +#: ../../content/applications/sales/rental.rst:61 +msgid "Rental products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:63 +msgid "To view all products that can rented in the database, navigate to :menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be Rented` search filter appears in the search bar." +msgstr "" + +#: ../../content/applications/sales/rental.rst:66 +msgid "Each product kanban card displays that product's name, rental price, and product image (if applicable)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:70 +msgid "Rental pricing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:72 +msgid "To adjust the rental pricing on a product, go to the :guilabel:`Products` page in the *Rental* app, then select the desired product or click :guilabel:`New` to create a new product from scratch." +msgstr "" + +#: ../../content/applications/sales/rental.rst:75 +msgid "On the product form, ensure the :guilabel:`Can be Rented` checkbox is ticked. Then, open the :guilabel:`Rental prices` tab." +msgstr "" + +#: ../../content/applications/sales/rental.rst:83 +msgid "If creating a rental product outside of the *Rental* app, just ensure the :guilabel:`Can be Rented` checkbox is ticked on the product form. By default, this checkbox is ticked whenever a product is created directly in the *Rental* application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:90 +msgid "Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, designate custom rental prices and rental periods for the product." +msgstr "" + +#: ../../content/applications/sales/rental.rst:93 +msgid "To add pricing for a rental, click :guilabel:`Add a price`. Then, choose a *pricing period* (:dfn:`the unit of duration of the rental`) in the :guilabel:`Period` column, or create a new pricing period by typing in the name and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:97 +msgid "Next, decide whether or not to apply this custom rental price to a specific :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:99 +msgid "Lastly, enter the desired :guilabel:`Price` for that specific :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:102 +msgid "There is no limit to how many pricing lines can be added. Multiple pricing options for rental products are typically used to give discounts for customers who agree to longer rental durations." +msgstr "" + +#: ../../content/applications/sales/rental.rst:105 +msgid "To delete any rental pricing option, click the :guilabel:`🗑️ (trash)` icon, and that row is deleted." +msgstr "" + +#: ../../content/applications/sales/rental.rst:109 +msgid "Reservations" +msgstr "" + +#: ../../content/applications/sales/rental.rst:111 +msgid "Under the :guilabel:`Reservations` section of the :guilabel:`Rental prices` tab, there is the option to configure additional fines for any :guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to return a rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:115 +msgid "There is also the option to set a :guilabel:`Security Time`, expressed in hours, to make the rental product temporarily unavailable between two rental orders. Such a feature may prove useful if maintenance or cleaning is required between rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:120 +msgid "Price computing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:122 +msgid "Odoo always uses two rules to compute the price of a product when a rental order is created:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:124 msgid "Only one price line is used." msgstr "" -#: ../../content/applications/sales/rental.rst:47 +#: ../../content/applications/sales/rental.rst:125 msgid "The cheapest line is selected." msgstr "" -#: ../../content/applications/sales/rental.rst:50 +#: ../../content/applications/sales/rental.rst:128 msgid "Consider the following rental pricing configuration for a product:" msgstr "" -#: ../../content/applications/sales/rental.rst:52 +#: ../../content/applications/sales/rental.rst:130 msgid "1 day: $100" msgstr "" -#: ../../content/applications/sales/rental.rst:53 +#: ../../content/applications/sales/rental.rst:131 msgid "3 days: $250" msgstr "" -#: ../../content/applications/sales/rental.rst:54 +#: ../../content/applications/sales/rental.rst:132 msgid "1 week: $500" msgstr "" -#: ../../content/applications/sales/rental.rst:56 +#: ../../content/applications/sales/rental.rst:134 msgid "A customer wants to rent this product for eight days. What price will they pay?" msgstr "" -#: ../../content/applications/sales/rental.rst:58 +#: ../../content/applications/sales/rental.rst:136 msgid "After an order is created, Odoo selects the second line as this is the cheapest option. The customer has to pay three times '3 days' to cover the rental's eight days, for a total of $750." msgstr "" -#: ../../content/applications/sales/rental.rst:64 +#: ../../content/applications/sales/rental.rst:142 +msgid "Rental orders" +msgstr "" + +#: ../../content/applications/sales/rental.rst:144 +msgid "To create a rental order in the *Rental* app, navigate to :menuselection:`Rental app --> Orders --> Orders`, and click :guilabel:`New`. Doing so reveals a blank rental order form to be filled in accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:-1 +msgid "Sample of a filled out rental order available in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:152 +msgid "Start by adding a :guilabel:`Customer`, then configure the desired duration of the rental in the :guilabel:`Rental period` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:155 +msgid "To adjust the rental duration, click the first date in the :guilabel:`Rental period` field, and select the range of dates to represent the rental duration from the pop-up calendar form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:-1 +msgid "Sample of a rental period calendar pop-up window in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:163 +msgid "Once complete, click :guilabel:`Apply` in the calendar pop-up form. Following that, the pop-up form disappears, and the designated time period of the rental is represented in the :guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:167 +msgid "Next, add a rental product in the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and selecting the desired rental product to add to the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst:171 +msgid "If a rental product is added *before* the :guilabel:`Rental period` field has been properly configured, the user can *still* adjust the :guilabel:`Rental period` field accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:174 +msgid "Simply select the desired range of dates to represent the duration of the rental, then click :guilabel:`Update Rental Prices` in the :guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:-1 +msgid "The update rental prices option that appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:181 +msgid "Doing so reveals a :guilabel:`Confirmation` pop-up window. If everything is correct, click :guilabel:`Ok`, and Odoo recalculates the rental price accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:184 +msgid "Once all the information has been entered correctly on the rental order form, click the :guilabel:`Send by Email` button to send the quotation to the customer, or click the :guilabel:`Confirm` button to confirm the order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:189 msgid "Customer signature" msgstr "" -#: ../../content/applications/sales/rental.rst:66 -msgid "You can ask your customers to sign a rental agreement outlining the arrangement between you and your customers before they pick up products to make sure your products are returned on time and in their original condition. To do so, go to :menuselection:`Rental --> Configuration --> Settings`, activate *Digital Documents*, and *Save*." +#: ../../content/applications/sales/rental.rst:191 +msgid "Upon confirming a rental order, the :guilabel:`Sign Documents` button appears. This gives the ability to request the customer sign a rental agreement, outlining the arrangement between the company and customer, *before* they pick up the rental product(s)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:195 +msgid "Such documents can ensure everything is returned on-time and in its original condition." +msgstr "" + +#: ../../content/applications/sales/rental.rst:198 +msgid "The :guilabel:`Sign Documents` button/option **only** appears if the :guilabel:`Digital Documents` feature has been activated in the *Rental* application settings. To do so, navigate to :menuselection:`Rental app --> Configuration --> Settings`, activate :guilabel:`Digital Documents`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:204 +msgid "This feature also requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo automatically installs it after activating the :guilabel:`Digital Documents` setting." +msgstr "" + +#: ../../content/applications/sales/rental.rst:207 +msgid "To request a customer signature on a rental agreement, select a confirmed rental order, and click the :guilabel:`Sign Documents` button to reveal a :guilabel:`Sign Documents` pop-up window." msgstr "" #: ../../content/applications/sales/rental.rst:-1 -msgid "Digital Documents settings in Odoo Rental" +msgid "The Sign Documents pop-up window that appears in the Odoo Rental application." msgstr "" -#: ../../content/applications/sales/rental.rst:76 -msgid "This feature requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo installs it after activating *Digital Documents*." +#: ../../content/applications/sales/rental.rst:214 +msgid "From here, select the desired document from the :guilabel:`Document Template` field. Then, click :guilabel:`Sign Document`. Doing so reveals a :guilabel:`New Signature Request` pop-up window." msgstr "" -#: ../../content/applications/sales/rental.rst:79 -msgid "Once the app settings are saved, you have the option to change the default *Rental Agreement* from the dropdown menu. You can pick any document already uploaded to the *Sign* app, or upload a new one to the *Sign* app by clicking on *Upload Template*." +#: ../../content/applications/sales/rental.rst:-1 +msgid "The New Signature Request pop-up window that appears in the Odoo Rental application." msgstr "" -#: ../../content/applications/sales/rental.rst:83 -msgid "To request a customer signature, select a confirmed rental order, click on *Sign Documents*, choose the document template and click on *Sign Documents* again. On the next window, select your customer and click on *Sign Now* to start the signing process with your customer. Once the document is completed, click on *Validate & Send Completed Document*." +#: ../../content/applications/sales/rental.rst:221 +msgid "Upon confirming the information in the :guilabel:`New Signature Request` pop-up form, click :guilabel:`Sign Now` to initiate the signing process." +msgstr "" + +#: ../../content/applications/sales/rental.rst:224 +msgid "A separate page is then revealed, showcasing the document to be signed, which is accessible to the customer via the customer portal." +msgstr "" + +#: ../../content/applications/sales/rental.rst:227 +msgid "Odoo guides the customer through the signing process with clear, clickable indicators, and allows them to create electronic signatures to quickly complete the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst:-1 +msgid "The adopt your signature pop-up window that appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:234 +msgid "Once the document has been signed and completed, click the :guilabel:`Validate & Send Completed Document` button at the bottom of the document." +msgstr "" + +#: ../../content/applications/sales/rental.rst:-1 +msgid "The validate and send completed document button in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:241 +msgid "Upon clicking the :guilabel:`Validate & Send Completed Document` button, Odoo presents the option to download the signed document for record-keeping purposes, if necessary." msgstr "" -#: ../../content/applications/sales/rental.rst:89 +#: ../../content/applications/sales/rental.rst:245 msgid "`Odoo Tutorials: Sign `_" msgstr "" -#: ../../content/applications/sales/rental.rst:94 -msgid "Pickup and Return receipt" +#: ../../content/applications/sales/rental.rst:250 +msgid "Pickup products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:252 +msgid "When a customer picks up the product(s), navigate to the appropriate rental order, click the :guilabel:`Pickup` button, and then click :guilabel:`Validate` in the :guilabel:`Validate a pickup` pop-up form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:256 +msgid "Doing so places a :guilabel:`Picked-up` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:259 +msgid "Return products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:261 +msgid "When a customer returns the product(s), navigate to the appropriate rental order, click the :guilabel:`Return` button, and validate the return by clicking :guilabel:`Validate` in the :guilabel:`Validate a return` pop-up form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:265 +msgid "Doing so places a :guilabel:`Returned` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:268 +msgid "Print pickup and return receipts" msgstr "" -#: ../../content/applications/sales/rental.rst:96 -msgid "You can print and give your customers receipts when they pick up and/or return products. To do so, open any rental order, click on *Print* and select *Pickup and Return Receipt*. Odoo then generates a PDF detailing all information about the current status of the rented items: which were picked up, when they are expected to be returned, which were returned, and potential rental delay costs." +#: ../../content/applications/sales/rental.rst:270 +msgid "Pickup and return receipts can be printed for customers when they pick up and/or return rental products." +msgstr "" + +#: ../../content/applications/sales/rental.rst:273 +msgid "To print pickup and/or return receipts, navigate to the appropriate rental order, click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu." msgstr "" #: ../../content/applications/sales/rental.rst:-1 -msgid "Printing a Pickup and Return receipt in Odoo Rental" +msgid "The pickup and return receipt print option in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:280 +msgid "From this drop-down menu, hover over the :guilabel:`Print` option to reveal a sub-menu. Then select :guilabel:`Pickup and Return Receipt`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:283 +msgid "Odoo generates and downloads a PDF, detailing all information about the current status of the rented item(s)." msgstr "" #: ../../content/applications/sales/sales.rst:10 @@ -5044,289 +5354,387 @@ msgid "Amazon Connector" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:3 -msgid "Amazon Connector Features" +msgid "Amazon Connector features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:5 -msgid "The **Amazon Connector** synchronizes the orders between Amazon and your Odoo database, which reduces considerably the amount of time spent on your Amazon Seller Central dashboard, making your daily routine a lot easier." +msgid "The *Amazon Connector* synchronizes orders between Amazon and Odoo, which considerably reduces the amount of time spent manually entering Amazon orders (from the Amazon Seller account) into Odoo. It also allows users to accurately keep track of Amazon sales in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:10 -msgid "Supported Features" +msgid "Supported features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:12 -msgid "The connector is able to:" +msgid "The Amazon Connector is able to:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:14 -msgid "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM) and their order items which include:" +msgid "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM), and their order items, which include:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:17 -msgid "the product’s name, description and quantity" +msgid "product name, description, and quantity" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:18 -msgid "the shipping costs for the product" +msgid "shipping costs for the product" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:19 -msgid "the gift wrapping charges" +msgid "gift wrapping charges" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:21 -msgid "Create on Odoo any missing partner related to an order (contact types supported: contact and delivery)." +msgid "Create any missing partner related to an order in Odoo (contact types supported: contact and delivery address)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:23 -msgid "Notify Amazon of a shipping confirmed on Odoo (FBM) in order to get paid." +#: ../../content/applications/sales/sales/amazon_connector/features.rst:24 +msgid "Notify Amazon of confirmed shipment in Odoo (FBM) to get paid." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:25 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:26 msgid "Synchronize (Odoo to Amazon) all available quantities of your products (FBM)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:27 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:28 msgid "Support multiple seller accounts." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:28 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:30 msgid "Support multiple marketplaces per seller account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:32 +msgid "The following table lists capabilities provided by Odoo when using the Amazon Connector:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 msgid "Fulfilled By Amazon (FBA)" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 msgid "Fulfilled By Merchant (FBM)" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:33 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 msgid "**Orders**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:33 -msgid "Synchronize shipped and canceled orders" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize shipped and canceled orders." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:33 -msgid "Synchronize unshipped and canceled orders" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize unshipped and canceled orders." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:36 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 msgid "**Shipping**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:36 -msgid "Charges" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "Shipping cost is computed by Amazon, and included in the synchronized order." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 -msgid "Delivery created" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "Shipping cost is computed by Amazon and included in the synchronized orders." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:39 -msgid "**Gift Wrapping**" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "Shipping done by Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:39 -#: ../../content/applications/sales/sales/amazon_connector/features.rst:46 -msgid "Handled by Amazon" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "A delivery order is automatically created in Odoo for each new order. Once it has been processed in Odoo, the status is then synchronized in Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:39 -msgid "Gift wrapping charges" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "**Gift Wrapping**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 -msgid "Gift message" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Handled by Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:42 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "Cost is computed by Amazon, and included in the synchronized order. Gift message is added on a line of the order and on the delivery order. Then it is up to the user." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 msgid "**Stock Management**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:42 -msgid "One stock move created per sales order item" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "Managed by Amazon, and synchronized with a virtual location to follow it in Odoo." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:42 -msgid "Handled by the delivery" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "Managed in Odoo Inventory app, and synchronized with Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 -msgid "Products available quantity updated from Odoo to Amazon" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "**Delivery Notifications**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:46 -msgid "**Confirmation**" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Send by Amazon, based on delivery status synchronized from Odoo." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:46 -msgid "Notify Amazon when confirming delivery" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +msgid "The Amazon Connector is designed to synchronize the data of sales orders. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds, **must** be managed from the *Amazon Seller Central*, as usual." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:51 -msgid "The connector is designed to synchronize orders' data as detailed above. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds must be managed from Amazon Seller Central, as usual." +#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +msgid "Supported marketplaces" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:58 -msgid "Supported Marketplaces" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:75 +msgid "The Amazon Connector supports all the current marketplaces." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:60 -msgid "The Amazon Connector supports all the current marketplaces. If a marketplace is not listed in your Amazon marketplaces, you can :ref:`add a new marketplace `." +#: ../../content/applications/sales/sales/amazon_connector/features.rst:77 +msgid "If a marketplace is not listed in your Amazon marketplaces, it's possible to :ref:`add a new marketplace `." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:148 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:81 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 msgid ":doc:`setup`" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:67 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 msgid ":doc:`manage`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 -msgid "Manage Amazon orders in Odoo" +msgid "Amazon order management" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 -msgid "Synchronization of orders" +msgid "Order synchronization" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 -msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered." +msgid "Orders are automatically fetched from Amazon, and synchronized in Odoo, at regular intervals." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:10 +msgid "The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. This includes changes on either end (Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:13 +msgid "For *FBA* (Fulfilled by Amazon), only *Shipped* and *Canceled* orders are fetched." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 -msgid "When an order is canceled in Amazon and was already synchronized in Odoo, the corresponding sales order is automatically canceled in Odoo." +msgid "For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and *Canceled* orders. For each synchronized order, a sales order and customer are created in Odoo (if the customer is not already registered in the database)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:19 -msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the :ref:`developer mode `, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 +msgid "When an order is canceled in Amazon, and was already synchronized in Odoo, the corresponding sales order is automatically canceled in Odoo." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:25 -msgid "To synchronize immediately the orders of your Amazon account switch to :ref:`developer mode `, head to your Amazon account and click on **SYNC ORDERS**. The same can be done with pickings by clicking on **SYNC PICKINGS**." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:24 +msgid "Force synchronization" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 -msgid "Manage deliveries in FBM" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26 +msgid "In order to force the synchronization of an order, whose status has **not** changed since the previous synchronization, start by activating the :ref:`developer mode `. This includes changes on either end (Amazon or Odoo)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:32 -msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 +msgid "Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`), and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:36 -msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:34 +msgid "Be sure to pick a date that occurs prior to the last status change of the desired order to synchronize and save. This will ensure synchronization occurs correctly." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:40 -msgid "Amazon requires to provide a tracking reference with each delivery. You'll need to assign a carrier. If the carrier doesn't automatically provide a tracking reference, you'll need to set one manually. This concerns all marketplaces." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:39 +msgid "To immediately synchronize the orders of an Amazon account, switch to :ref:`developer mode `, head to the Amazon account in Odoo, and click :guilabel:`Sync Orders`. The same can be done with pickings by clicking :guilabel:`Sync Pickings`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:45 -msgid "If your chosen carrier isn't one supported by Odoo, you can still create a carrier bearing its name (e.g. create a carrier named `Colissimo`). This name is case insensitive, but be careful about typos, as Amazon won't recognize them." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:44 +msgid "Manage deliveries in FBM" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:48 -msgid "Create a delivery carrier named `Self Delivery` to inform Amazon that you make your own deliveries. You still have to enter a tracking reference." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 +msgid "Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a picking is instantly created in the *Inventory* app, along with a sales order and customer record. Then, decide to either ship all the ordered products to the customer at once, or ship products partially using backorders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:50 -msgid "Keep in mind that the customer is notified by email about the delivery, and the carrier and tracking reference are displayed in the email to the customer." +msgid "When a picking related to the order is confirmed, a notification is then sent to Amazon, who, in turn, notifies the customer that the order (or a part of it) is on its way." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgid "Amazon requires users to provide a tracking reference with each delivery. This is needed to assign a carrier." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:59 -msgid "Manage errors when synchronizing deliveries" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 +msgid "If the carrier doesn't automatically provide a tracking reference, one must be set manually. This rule applies to all Amazon marketplaces." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:61 +msgid "If the chosen carrier isn't supported by Odoo, a carrier with the same name can still be created (e.g. create a carrier named `easyship`). The name used is **not** case sensitive, but be mindful to avoid typos. If there are typos, Amazon will **not** recognize them. Next, create a delivery carrier named `Self Delivery` to inform Amazon that the user will make the deliveries. Even with this route, a tracking reference still **must** be entered. Remember, the customer is notified by email about the delivery, and the carrier, along with the tracking reference, are displayed in the email to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:70 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75 +msgid "Manage errors when synchronizing deliveries" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:77 msgid "Sometimes, Amazon can fail to correctly process all the information sent by Odoo. In this case, Odoo sends an email listing all the shipments that failed and the errors Amazon sent with them. In addition, these shipments are flagged with a :guilabel:`Synchronization with Amazon failed` tag." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:65 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 msgid "Usually, the error can be corrected directly in the Amazon backend or in Odoo. If the problem is corrected in Odoo, synchronize the shipment again using the :guilabel:`Retry Amazon Sync` button." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:69 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:85 msgid "It might happen that Odoo receives a notification from Amazon saying that some delivery information was not processed, but without specifying which shipments were affected. In that case, all the shipments in an unknown state will be treated as if they failed to synchronize. Once Odoo receives a notification from Amazon saying that a shipment was processed, its tag will change to :guilabel:`Synchronized with Amazon`. To speed up this process, on your Amazon account, click on :guilabel:`Sync Orders` to manually synchronize these orders, or click on :guilabel:`Recover Order` and enter the relevant Amazon Order Reference." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:78 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:94 msgid "Follow deliveries in FBA" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:80 -msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +msgid "When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded in the *Inventory* app for each sales order item. That way, it's saved in the system." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:99 +msgid "Inventory managers can access these stock moves by navigating to :menuselection:`Inventory app --> Reporting --> Moves History`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102 +msgid "For FBA orders, the stock move is automatically created in Odoo by the Amazon connector, thanks to the shipping status of Amazon. When sending new products to Amazon, the user should manually create a picking (delivery order) to transfer these products from their warehouse to the Amazon location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:107 +msgid "To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after replenishing stock. An automated replenishment from reordering rules can also be triggered on the Amazon location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:110 +msgid "The Amazon location is configurable by accessing the Amazon account managed in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:87 -msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 +msgid "All accounts of the same company use the same Amazon location, by default. However, it is possible to follow the stock filtered by marketplace." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:92 -msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:117 +msgid "To do that, first remove the marketplace, where the desired stock to follow separately can be found, from the list of synchronized marketplaces, which can be found by navigating to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:100 -msgid "Issue invoices and register payments" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:122 +msgid "Next, create another registration for this account, and remove all marketplaces--- **except** the marketplace this is desired to be isolated from the others." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:103 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:125 +msgid "Lastly, assign another stock location to the second registration of the account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128 +msgid "Invoice and register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 msgid "Issue invoices" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:105 -msgid "Sending invoices to Amazon customers directly from Odoo is not feasible due to Amazon's policy of not sharing customer email addresses. Instead, it is possible to manually upload the invoices generated on Odoo to the Amazon backend." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133 +msgid "Due to Amazon's policy of not sharing customer email addresses, it is **not** possible to send invoices directly to Amazon customers from Odoo. However, it **is** possible to manually upload the generated invoices from Odoo to the Amazon back-end." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:137 +msgid "Additionally, for B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon back-end **before** creating an invoice in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:141 +msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:109 -msgid "In addition, for your B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon backend before creating the invoice in Odoo." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:146 +msgid "TaxCloud integration will be decommissioned in Odoo 17+." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:113 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 msgid "Register payments" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:115 -msgid "As customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (for example, named `Amazon payments`) with a dedicated *Bank and Cash* intermediary account is recommended." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151 +msgid "Since customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* intermediary account is recommended." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:118 -msgid "In addition, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments. Use the dedicated `Amazon payments` :guilabel:`Journal` and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`. Then, select all the payments generated and click :menuselection:`Actions --> Create batch payment --> Validate`." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:154 +msgid "Additionally, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:125 -msgid "The same can be done with vendor bills from Amazon dedicated to commissions. When the balance is received in the bank account at the end of the month and the banks statements are recorded, credit the Amazon intermediary account by the amount received." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:157 +msgid "To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:160 +msgid "Then, select all the generated payments, and click :menuselection:`Actions --> Create batch payment --> Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:164 +msgid "This same action can be performed with vendor bills from Amazon dedicated to commissions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 +msgid "When the balance is received in the bank account at the end of the month, and the bank statements are recorded, credit the Amazon intermediary account by the amount received." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:130 -msgid "Follow your Amazon sales in sales reporting" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:170 +msgid "Follow Amazon sales in sales reporting" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:132 -msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 +msgid "On the Amazon account profile in Odoo, a sales team is set under the :guilabel:`Order Follow-up` tab." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:136 -msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:175 +msgid "This gives quick access to important metrics related to sales reporting. By default, the Amazon account's sales team is shared between all of the company's accounts." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:140 -msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:178 +msgid "If desired, the sales team on the account can be changed for another, in order to perform a separate reporting for the sales of this account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:147 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:182 +msgid "It is also possible to perform reporting on a per-marketplace basis." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 +msgid "First, remove the desired marketplace from the list of synchronized marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:186 +msgid "To access the list of synchronized marketplaces in Odoo, navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:189 +msgid "Then, create another registration for this account, and remove all other marketplaces **except** the one to isolate." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:192 +msgid "Lastly, assign another sales team to one of the two registrations of the account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:195 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 msgid ":doc:`features`" msgstr "" @@ -5476,7 +5884,6 @@ msgid "All marketplaces are supported by the Amazon Connector. To add a new mark msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 msgid "Activate the :ref:`developer mode `." msgstr "" @@ -5508,208 +5915,974 @@ msgstr "" msgid "eBay Connector" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 -msgid "How to list a product?" +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:3 +msgid "Linking existing listings" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:6 -msgid "Listing without variation" +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:5 +msgid "Once the eBay account is linked existing listings from within the eBay seller account need to be added manually to the Odoo product listings." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:8 -msgid "In order to list a product, you need to check the **use eBay** field on a product form. The eBay tab will be available." +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:8 +msgid "The process will be as follows: - Turn off eBay scheduled actions - Add products and link listings - Turn on eBay scheduled actions" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 -msgid "When the **Use Stock Quantity** field is checked, the quantity sets on eBay will be the Odoo **Forecast Quantity**." +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:14 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:28 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:15 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:6 +msgid "To learn more about the eBay connector visit these pages as well:" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 -msgid "The **Description Template** allows you to use templates for your listings. The default template only use the **eBay Description** field of the product. You can use html inside the **Description Template** and in the **eBay Description**." +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:32 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:19 +msgid ":doc:`troubleshooting`" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:21 -msgid "To use pictures in your listing, you need to add them as **Attachments** on the product template." +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:21 +msgid "Turn off eBay scheduled actions" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:24 -msgid "Listing with variations" +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:23 +msgid "To start linking existing listings in eBay, first turn off the eBay notifications in the scheduled actions in Odoo. The reason for this is so that no orders or eBay data syncs during this process. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode `. After doing so, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:30 +msgid ":doc:`../../../general/developer_mode` must be activated to ensure the technical menu appears for the user." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:33 +msgid "Disabling scheduled actions enables users to sync and validate eBay data before receiving orders. The following are descriptions of scheduled actions that need to be temporarily deactivated:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:36 +msgid ":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo (based on :guilabel:`client_order_reference`, or :guilabel:`sales order reference` field). This command also updates existing orders, where changes we made in eBay. New and updated orders are then placed in draft mode. Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:40 +msgid ":guilabel:`eBay: synchronize stock`: eBay displays Odoo's stock on hand." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:41 +msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer; a manual update required for the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:44 +msgid "To toggle off the eBay notification, select the entry from the :guilabel:`Scheduled Actions` list. Then, on the page, click the :guilabel:`Active` toggle button to turn it off." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:48 +msgid "Sync eBay categories" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:50 +msgid "To ensure that Odoo's eBay products have all the categories available on eBay, the eBay categories should be synced to Odoo next." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:53 +msgid "Navigate to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`. Click into the scheduled action labeled: :guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`. This action will populate the :menuselection:`Sales --> Configuration --> eBay Categories` menu item with all standard eBay product categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:59 +msgid "Odoo only recognizes eBay category paths up to four layers deep. If a product has a listing of more than four, the category field will only populate up to the fourth layer." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:62 +msgid "If product categories beyond four paths are required, users need to manually add those paths. This has historically been done by getting a list of all product categories beyond 4 paths, manually importing them into the Product Category model in Odoo, then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:67 +msgid "Users can import the remaining product categories into the eBay product categories manually using using the :guilabel:`Action` menu and :guilabel:`Import` feature." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:71 +msgid "Link eBay listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:73 +msgid "To add eBay listings in Odoo, either manually add products, using a listing ID, or establish an automatic listing link between Odoo and eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:77 +msgid "For more information on listing a product from scratch visit: :ref:`How to list a product? `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:81 +msgid "Manual listing link" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:83 +msgid "To add an eBay listing to products in Odoo, begin by going to :menuselection:`Sales app --> Products --> Products` and selecting the desired product. Click on :guilabel:`Sell on eBay` (either in the :guilabel:`eBay` tab or under the :guilabel:`Product name`). Select :guilabel:`Save` if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:87 +msgid "Still the product form, click :guilabel:`link to listing` in the top menu and enter in listing ID from eBay in the pop up (the listing ID is in the eBay product URL)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:91 +msgid "An example URL would be as such: `www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The listing ID is `272222656444` in this case. Once the listing ID has been entered the eBay listing information will sync into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:97 +msgid "Turn on eBay scheduled Actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:99 +msgid "The next step is to turn on the eBay notifications in the scheduled actions in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode ` and go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:104 +msgid "Turning on the following scheduled actions allows users to sync and validate eBay data automatically." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:107 +msgid ":guilabel:`eBay: get new orders`: eBay will push all new orders not already in Odoo (based on client_order_reference, or sales order reference field), and will update orders if there has been a change from eBay. Orders will be put in draft mode. Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:111 +msgid ":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:112 +msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer, will need to manually update the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:116 +msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *Sales Order* while in draft state to represent a storable product, and then the user can link to the listing as they come in." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:26 -msgid "When the **use eBay** on a product with variations is checked and with **Fixed Price** as **Listing Type**, the eBay form is slightly different. In the variants array, you can choose which variant will be listed on eBay as well as set the price and the quantity for each variant." +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:127 +msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153 +msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:124 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 +msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 +msgid "How to list a product?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:7 +msgid "In order to list a product on eBay and Odoo there are two methods in Odoo to do so:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:9 +msgid "Make a product in Odoo and list the item eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:11 +msgid "Click :guilabel:`List Item on eBay` in the top menu of the product template. The product template can be accessed by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 +msgid "List the item on eBay, then create the product in Odoo, and finally link product to the item on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 +msgid "Click :guilabel:`Link With Existing eBay Listing` in the top menu on the product template.The product template can be accessed by navigating to :menuselection:`Sales app --> Product --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:22 +msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *sales order* while in draft state to represent a storable product, and then the user can link to the listing as they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:31 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:10 +msgid ":doc:`linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 -msgid "Listing with item specifics" +msgid "Listing without variation" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 -msgid "In order to add item specifics, you should create a product attribute with one value in the **Variants** tab on the product form." +msgid "Access the product template by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:44 -msgid "Product Identifiers" +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:40 +msgid "In order to list a product, select the :guilabel:`Sell on eBay` field on a product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if necessary." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:46 -msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay category. The module manages the EAN and UPC identifiers with the **Barcode** field of the product variant. If the **Barcode** field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay. The Brand and MPN values are working as item specifics and should be define in the **Variants** tab on the product form. If these values are not set, 'Does not apply' will be used for the eBay listing." +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:-1 +msgid "The eBay template form listed in the product template in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:48 +msgid "When the :guilabel:`Use Stock Quantity` field is checked, the quantity set on eBay will be the Odoo *Forecast Quantity* (Odoo *Inventory* app)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:51 +msgid "The :guilabel:`Description Template` allows the administrator to use templates in listings. The default template only use the :guilabel:`eBay Description` field of the product. HTML can be used inside the :guilabel:`Description Template` and in the :guilabel:`eBay Description` in Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in the template and description. Simply type a forward slash `/` to reveal a menu with formatting, layout, and text options. To add an image, type `/image`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:58 +msgid "To use images in the listing, another option is to add them as *Attachments* on the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:62 +msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/email_communication/email_template`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 +msgid "Listing with variations" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68 +msgid "When the :guilabel:`Sell on eBay` is checked on a product containing variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the eBay form is slightly different. Go to the :guilabel:`Variants` tab to or click :guilabel:`Configure Variants` in the top menu to configure the variant settings. Pricing can be configured for each variation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 +msgid "When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in which the :guilabel:`Fixed Price` can be entered, and the decision to :guilabel:`Publish on eBay` can be made for specific variants, along with other options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:-1 +msgid "The fixed price listing type in the eBay tab on a product form in Odoo sales." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:83 +msgid "Product identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85 +msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:88 +msgid "EAN and UPC identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 +msgid "The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` field of the product variant. If the :guilabel:`Barcode` field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:94 +msgid "Barcodes can be found on the product template, under the the :guilabel:`General Information` tab. Access the product template, first, by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:99 +msgid "Listing with item specifics" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 +msgid "In order to add item specifics, one should create a product attribute with a single value in the :guilabel:`Attributes & Variants` tab on the product form. Examples of item specifics include: `MPN` or `Brand`. The Brand and MPN values are working as item specifics and should be defined in the :guilabel:`Attributes & Variants` tab on the product form. If these values are not set, 'Does not apply' will be used for the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 +msgid "Process invoices and payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111 +msgid "Posting payment" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113 +msgid "When eBay orders are placed they are always paid for up front, via the eBay site. At no point will users pay for items on eBay through Odoo. Therefore, once orders are synced into Odoo from eBay they are already paid for. Odoo's invoicing and payment functionalities are not utilized. However, invoices need to be created and marked as Paid to “close” the *Sales Order*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 +msgid "Users can opt to mass create and post invoices in batches. To do so, navigate to Quotations in the list view by going to :menuselection:`Sales app --> Orders --> Quotations`. In the upper right corner, select the list view icon. Hover over the icons to reveal the name of each. Then check the boxes on the left that invoices should be made for and go to the :guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create Invoices`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:124 +msgid "A pop-up will appear and click on the :guilabel:`Create and view invoice` button. A new screen will populate with the newly created invoices. Next, select all of them by clicking on the box icon next to :guilabel:`Number` in the header row of the list, this will select all the records. Then navigate to the :guilabel:`Action` menu and click :guilabel:`Post entries`. Following this step, a pop-up will appear and click on :guilabel:`Post journal entries`. This will take the invoices out of *draft* and set them to *posted*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:132 +msgid "Reconciling payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134 +msgid "Users typically utilize PayPal to receive payment from eBay, and then send lump sums from PayPal into their bank account. To reconcile this income, users can reconcile the one PayPal transfer with all related invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:138 +msgid "First navigate to the :guilabel:`Accounting Dashboard` by going to the :menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on :guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:143 +msgid "For the :guilabel:`Ending Balance` field, enter the same account that was entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, open the new balance that needs to be reconciled. Under the tab marked: :guilabel:`Match Existing Entries` select the entries that are included in this balance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:148 +msgid "After adding all the necessary entries, click :guilabel:`Validate` to complete the reconciliation. To verify the payment, navigate to :menuselection:`Customers --> Invoices` and select the desired customer invoice. The *Paid* label should appear under the :guilabel:`Payment Status` column." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:154 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 +msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 -msgid "How to configure eBay in Odoo?" +msgid "eBay connector setup" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 -msgid "Create eBay tokens" +msgid "Overview" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 -msgid "In order to create your tokens, you need to create a developer account on the `developer portal `_. Once you are logged in, you can create **Sandbox Keys** and **Production Keys** by clicking on the adequate buttons." -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:16 -msgid "After the creation of the keys, you can get the user token. To do so, click on the **Get a User Token** link in the bottom of the page. Go through the form, log in with you eBay account and you will get the keys and token needed to configure the module in Odoo." +msgid "Odoo's eBay connector allows eBay listings to connect with Odoo products. Once connected, :doc:`updates to the listings ` can be made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* are created in Odoo for the user to review and confirm. Once the sales order is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull products out of inventory, and allow the user to create invoices." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 -msgid "Set up tokens in Odoo?" +msgid "eBay - Odoo linked fields" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 -msgid "To set up the eBay integration, go to :menuselection:`Sales --> Configuration --> Settings`." +msgid "The following are eBay product details. Each of these eBay fields update corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:27 +msgid "eBay URL" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:28 +msgid "eBay status" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 -msgid "First choose if you want to use the production or the sandbox eBay Site. Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert Key**. Apply the changes." +msgid "Quantity sold" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:30 +msgid "Start date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:31 +msgid "Title" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:32 +msgid "Subtitle" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 -msgid "Once the page is reloaded, you need to synchronize information from eBay. Push on **Sync countries and currencies**, then you can fill in all the other fields." +msgid "Item condition" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:34 +msgid "Category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:35 +msgid "Category 2" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 -msgid "When all the fields are filled in, you can synchronize the categories and the policies by clicking on the adequate buttons." +msgid "Store category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:37 +msgid "Store category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:38 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:39 +msgid "Seller profiles" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 -msgid "Accept account deletion notifications" +msgid "Postal code" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:41 +msgid "Shipping policy" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 -msgid "Since September 2021, **eBay requires supporting customer account deletion/closure notifications**. As such, when eBay receives an account request for deletion, all eBay partners must confirm the reception of the request and take further action if necessary." +msgid "Listing type (fixed price or auction)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:44 +msgid "Starting price for Auction" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:45 +msgid "Buy it now price" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 -msgid "Odoo has a notification endpoint to receive those notifications, confirm the reception of the request, and handle the first set of actions to anonymize the account details in **Contacts** and remove the customer's access to the portal." +msgid "Fixed Price amount" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:48 +msgid "Use stock quantity" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:49 +msgid "Quantity on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:50 +msgid "Duration" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 -msgid "Make sure to correctly :ref:`set up your subscription to the marketplace account deletion notifications ` as eBay may temporarily disable the related eBay account until the subscription is completed." +msgid "Allow best offer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 +msgid "Private listing" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 +msgid "eBay description" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 +msgid "eBay product image" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:55 +msgid "Country" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 -msgid "Retrieve endpoint details from Odoo" +msgid "eBay terms" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 -msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. Click on *Generate Token* to retrieve your **Verification Token**." +msgid "*Variations* group multiple products into one, with variation (or variant) options. Variations can sync to Odoo's attributes and values. Variations will appear in drop down menus near the top of the page when viewing an eBay listing. These are comparable to product variants in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Button to generate an eBay verification token in Odoo" +msgid "An example on eBay of the variations that can be added to a product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:70 -msgid "Subscribe to account deletion notifications" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:68 +msgid "*Item specifics*, located at the bottom of the listing, detail product-specific information. These specifics don't sync with Odoo fields by default; a development is required to link these fields." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Item specifics listed on an eBay product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:75 +msgid "*Sandbox* and *Production* are terms that are used to categorize the eBay environments as either still in development/testing (*Sandbox*) or for use in the real instance of the database with real customer information/dataset (*Production*). It is recommended to start first in the *Sandbox* to test, and then following the processes below, create a *Production* instance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 +msgid "eBay's sandbox environment can be accessed by navigating to `eBay's sandbox portal `_ at `https://sandbox.ebay.com/`. eBay's production environment can be accessed by navigating to `eBay.com portal `_ or `https://www.ebay.com/`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:87 +msgid "The environment selection **must** remain the same for all environment settings on eBay and on Odoo throughout this setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:91 +msgid "eBay actions available on Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:93 +msgid "The following are built-in actions in Odoo that add or update eBay listings:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 +msgid "**List**/ **Link**: generate a new eBay listing with an Odoo product by clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay Listing`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 +msgid ":guilabel:`Revise item` button: after making changes to an eBay listing in Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to update the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:99 +msgid "**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` was not selected, a user can relist the item from Odoo. The start date will reset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:101 +msgid ":guilabel:`End item's listing` button: end a listing on eBay directly from Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:102 +msgid "**Unlink product listings**: users can unlink a product from the eBay listing; the listing will stay intact on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:106 +msgid "Setup required on Odoo prior to eBay setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:108 +msgid "To link eBay with Odoo, install the eBay module by navigating to the Odoo dashboard and clicking into the :guilabel:`Apps` application. Search the term `eBay` and install the `eBay Connector` module." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:72 -msgid "Log in on the `developer portal of eBay `_ and go to **Alerts & Notifications**." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 +msgid "The following items must be configured before eBay is set up:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:114 +msgid "In Odoo, create and configure products that are intended to be listed in eBay. eBay does not import new products into Odoo. All products must first be created in Odoo, and then linked to listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 +msgid "Odoo does not allow multiple eBay listings to be linked per product in Odoo. If the company sells the same product for multiple listings, follow these instructions:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 +msgid "Set up one *base* product (noted in the :guilabel:`Component` field of the :abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull from. This will be a storable product so stock can be kept. Highlighted in green below, this product will be included in the kit on each subsequent “linked” product below." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 +msgid "Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the :abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type will be determined by the company's accounting settings, as explained in the Odoo documentation. Highlighted in yellow below, each product should have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base product as a :guilabel:`Component` of the kit. When this linked eBay product is sold, the delivery order created will have the base product listed in lieu of the linked product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:0 +msgid "Setting up bill of materials with base product and linked products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:138 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/management/bill_configuration/`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 +msgid "eBay does not automatically create invoices for eBay orders that get pushed into Odoo. Set invoicing policy on eBay products: invoicing policy will dictate when the product can be invoiced. Since most eBay users collect payment before the product is shipped, “invoice on ordered” will allow users to mass create invoices for eBay orders every day." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:144 +msgid "Set the :guilabel:`Outgoing Shipments` route for the warehouse to :guilabel:`Deliver goods directly (1 step)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:148 +msgid "When the :guilabel:`Outgoing Shipments` route is set to two or three steps, a known bug occurs: eBay wrongly marks orders as delivered when the pick operation in Odoo is confirmed. The expected behavior is to mark orders as delivered **after** the *delivery order* is confirmed. This mislabeling prevents tracking numbers in eBay from being imported onto the delivery order." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:152 +msgid "If the Accounting/Invoicing apps are installed, practice registering payment and reconciling invoices created from eBay orders with incoming eBay money." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:156 +msgid ":doc:`../../..//finance/accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:158 +msgid "Generate a marketplace account deletion/closure notification token. To begin, navigate to :menuselection:`Sales app --> Configuration --> Settings`. Under the :guilabel:`eBay` heading, change the mode to :guilabel:`Production`, and input random text values for the :guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` button under the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` section. This token will be used during the setup on eBay for the deletion/closure notifications configuration." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Overview of the Alerts & Notifications dashboard of eBay" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Generate a verification token in Odoo." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:79 -msgid "To subscribe to deletion/closure notifications, eBay needs a few details:" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:170 +msgid "Set up on eBay" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 -msgid "An **email address** to send notifications to if the endpoint is unreachable." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:173 +msgid "Set up eBay developer account" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:82 -msgid "The **endpoint details**:" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:175 +msgid "To start, create an eBay developer account via `eBay's developer portal `_. This site requires a different login and password than the eBay account, though the same email address can be used to register. The verification to create a developer account is around 24 hours." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:84 -msgid "The URL to Odoo's account deletion notification endpoint" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:181 +msgid "Set up eBay keyset" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:85 -msgid "A verification token" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:183 +msgid "Once the eBay developer account is created, set up an application on `eBay's developer portal `_. Next, navigate to the :guilabel:`Hi [username]` heading at top right of screen, then from the drop-down menu options, click :guilabel:`Application Keysets`. Doing so opens a pop-up that prompts the user to :guilabel:`Enter Application Title` (up to fifty characters), and choose a development environment (:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate first keyset. This application title is not saved until the keyset is generated. Click on :guilabel:`Create a keyset` to generate the keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:192 +msgid "The newly created *production keyset* is disabled by default. Activate it by subscribing to the eBay Marketplace 'account deletion or closure notifications' or by applying to eBay for an exemption. Once enabled, the database can make 5000 calls per day using this keyset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Dedicated fields to enter the endpoint details" +msgid "Disabled keyset present after creating a keyset." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:92 -msgid "You can edit the last two fields once the email address field is filled out." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:201 +msgid "Configure account deletion / notification settings (Production)" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 -msgid "Verify the connectivity with the endpoint" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:203 +msgid "To configure notifications or delete the database on a production environment, navigate to the `eBay developer portal `_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`Application Keysets`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:208 +msgid "Next, click the :guilabel:`marketplace deletion/account closure notification` option under the :guilabel:`Production` keyset column. Enter an email under :guilabel:`Email to notify if marketplace account deletion notification endpoint is down`. Click :guilabel:`Save` to enable the email." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:212 +msgid "Following this action, enter the :guilabel:`Marketplace account deletion notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in Odoo by navigating to :menuselection:`Sales app --> Configuration --> Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:217 +msgid "Clicking the :guilabel:`Generate Token` button in Odoo below this field creates a verification token for the eBay production environment. In Odoo, :guilabel:`Copy` the newly created token and navigate to eBay to fill in the :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the :guilabel:`Event Notification Delivery Method`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Configuring account deletion / notification settings in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:226 +msgid "After completing the above fields, click :guilabel:`Send Test Notification` to test the new notifications. Proceed to the next step when the green check mark appears. Revisit the above settings if the test post is not as expected." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:230 +msgid "After configuring notification settings, go back to the :menuselection:`Application Keys` page to generate production keysets." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:234 +msgid "Creating the keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:236 +msgid "A successful setup of the notifications enables the ability to create Production Keysets which are needed in the remainder of the Odoo configuration. Navigate back to the :menuselection:`Application Keys` page generate a production keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:240 +msgid "The administrator is prompted to :menuselection:`Confirm the Primary Contact`. Enter or confirm the account owner (the person legally responsible for the eBay API License Agreement). Fill out :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select either the :guilabel:`Individual` or :guilabel:`Business` options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:246 +msgid "The provided email address or phone number does **not** have to match the account's. eBay uses this information to contacting the business or individual in case of issues with user tokens. Additional contacts can be added from the :guilabel:`Profile & Contacts` page on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:250 +msgid "Click on :guilabel:`Continue to Create Keys` to confirm the primary contact. The :guilabel:`Application Keys` populates in a new screen and an email is also sent to the developer account. An :guilabel:`App ID (Client ID)`, :guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Application keys are populated after creating the app in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:259 +msgid "Copy these values down as they will be input into Odoo later in the process." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:262 +msgid "Create eBay user token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:264 +msgid "Now, create a *user token* in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`User Access Tokens`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Generate user token s on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:271 +msgid "Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing or :guilabel:`Production` for the live database. Maintain the same selection for all environment settings on both eBay and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:275 +msgid "Next, select the radio button labeled :guilabel:`Auth'n'Auth`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:277 +msgid "Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` to get a user token in the chosen environment. This button varies based on the selection made above for either :guilabel:`Sandbox` or :guilabel:`Production`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:281 +msgid "Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal Address`. Complete the required fields, which are :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`, and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either :guilabel:`Individual` or :guilabel:`Business`. To complete the confirmation, click :guilabel:`Sign into eBay to get a Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:288 +msgid "eBay will contact this individual or business should there be any issues with the application keys. Other contacts can be added on the :menuselection:`Profile & Contacts` eBay page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:291 +msgid "The administrator will be redirected to either a sandbox or production sign-in page for eBay. This login is different than the eBay developer's console, it is the eBay account where the items will be sold on. This email and/or login can differ from the eBay developer account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:295 +msgid "Enter the :guilabel:`Email` or :guilabel:`Username` for the eBay account and sign into the eBay account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:299 +msgid "Should an additional user be needed for the sandbox simulation, a test user needs to be created. Visit `eBay's Register for Sandbox form `_. Detailed instructions can be found on eBay's help pages: `Create a test Sandbox user `_." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:305 +msgid "Grant application access" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:307 +msgid "After signing into the production or sandbox environment, eBay presents the administrator with an *agreement* to grant access to the user's eBay data." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:310 +msgid "Clicking :guilabel:`Agree` allows eBay to link the eBay account with the *application programming interface* (API). This agreement can be changed at any time by visiting eBay's account preferences." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:314 +msgid "eBay has a timed sequence between signing in and agreeing to the terms for the :abbr:`API (Application Programming Interface)` linkage to the account. Once complete a :guilabel:`User Token` will populate on the :menuselection:`User Tokens` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:318 +msgid "A :guilabel:`User Token` will populate on the screen. Make sure to copy this token down as it will be used in the next steps along with the :guilabel:`Application Keyset`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Generated user token and API explorer link on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:326 +msgid "Signing in to the eBay account is necessary to create to the token. The eBay developer can also revoke the token by clicking on the :guilabel:`Revoke a Token` link." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:330 +msgid "API explorer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:332 +msgid "Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have been created, a test can be executed via the `API Explorer `_ to ensure that the :abbr:`API (Application Programming Interface)` is configured correctly. This test will execute a simple search using the :abbr:`API (Application Programming Interface)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:338 +msgid "To begin the :abbr:`API (Application Programming Interface)` test, click on :guilabel:`Get OAuth Application Token`. This will populate the key into the :guilabel:`Token` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:341 +msgid "A basic search function is set to execute. Click on :guilabel:`Execute` to complete the test. A successful test will respond with a :guilabel:`Call Response` of `200 OK` with a corresponding :guilabel:`Time`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:346 +msgid "Entering credentials into Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:348 +msgid "The previously copied :guilabel:`User Token` and :guilabel:`Application Keyset` are now ready to be entered into the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:351 +msgid "Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> eBay`) and paste the following credentials from eBay into the corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:358 +msgid "Platform" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:359 +msgid "Dev Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:360 +msgid "Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:361 +msgid "App Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:362 +msgid "Cert Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:363 +msgid "eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:364 +msgid "Dev ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:365 +msgid "User Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:366 +msgid "App ID (Client ID)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:367 +msgid "Cert ID (Client Secret)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:368 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:102 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:369 +msgid "Developer Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:370 +msgid "Production/Sandbox Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:371 +msgid "Production/Sandbox App Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:372 +msgid "Production/Sandbox Cert Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:375 +msgid "The :guilabel:`Application Keyset` can be accessed by going to `eBay's developer portal `_ and navigate to the `Hi [username]` at top right of screen, then click on :guilabel:`Application Keysets`. Get to the *User Token* in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`User Access Tokens` and click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also be accessed by clicking on :guilabel:`User Tokens` from the :menuselection:`Application Keys` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:382 +msgid "Confirm that the setup is correct by saving the credentials in Odoo. Once the initial setup is complete, a new menu tab in products will appear called `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` documentation on how to list products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:387 +msgid "Sync product categories by clicking :guilabel:`Product Categories`. After syncing, a new menu item, `eBay Category`, appears available for products to be configured with. These eBay categories are imported from the Odoo database and are available when listing an item on eBay through Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:393 +msgid "If Product Categories beyond four paths are required, users will need to manually add those paths. This has historically been done by getting a list of all product categories beyond four paths, manually importing them into the Product Category model in Odoo, and then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:399 +msgid "Now that the setup is complete, proceed to either:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:401 +msgid ":doc:`Create listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:402 +msgid ":doc:`Link existing listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:3 +msgid "Troubleshooting eBay connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:13 +msgid "Accept account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:15 +msgid "Since September 2021, **eBay requires supporting customer account deletion/closure notifications**. As such, when eBay receives an account request for deletion, all eBay partners must confirm the reception of the request and take further action if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:19 +msgid "Odoo has a notification endpoint to receive those notifications, confirm the reception of the request, and handle the first set of actions to anonymize the account details in *Contacts* and remove the customer's access to the portal." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:24 +msgid "Make sure to correctly :ref:`set up the subscription to the marketplace account deletion notifications ` as eBay may temporarily disable the related eBay account until the subscription is completed." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:29 +msgid "Verify the installation of Odoo is up to date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:31 +msgid "In order to activate the endpoint, the module *eBay Connector - Account Deletion* must be installed. If the Odoo database was first created after September 2021, the module is installed automatically and the administrator can proceed to the :ref:`next step `." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:36 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:38 +msgid "The notification endpoint is made available through a new Odoo module; to be able to install it, the administrator must make sure that the Odoo source code is up-to-date." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:41 +msgid "If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is already up-to-date, so proceed to the next step." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 +msgid "If the company uses Odoo with an on-premise setup or through a partner, then the administrator must update the installation as detailed in :doc:`this documentation page ` or by contacting an integrating partner." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:50 +msgid "New modules must be *discovered* by the Odoo instance to be available in the :menuselection:`Apps` menu." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:53 +msgid "To do so, activate the :ref:`developer mode `, and go to :menuselection:`Apps -> Update Apps List`. A wizard will ask for confirmation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:57 +msgid "Install the eBay Connector - Account Deletion update" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:60 +msgid "**Never** install new modules in the production database without 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, the administrator should use a staging or duplicate database. For on-premise users, the administrator should use a staging environment - contact the integrating partner for more information regarding how to test a new module in a particular setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:67 +msgid "To install the module, go to the :menuselection:`Apps` menu, remove the `Apps` search facet and search for `eBay`. If the module *eBay Connector - Account Deletion* is present and marked as installed, the Odoo database is already up-to-date and the administrator can proceed with the next step. If it is not yet installed, install it now." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:75 +msgid "Retrieve endpoint details from Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:77 +msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. First, input random text values for the :guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:89 +msgid "Subscribe to account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:91 +msgid "Navigate to the `eBay developer portal `_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at the top right of screen, then go to :guilabel:`Alerts & Notifications`." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 -msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the **Send Test Notification** button." +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Overview of the Alerts & Notifications dashboard of eBay" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:100 -msgid "You should get the following confirmation message: \"A test notification was sent successfully!\"" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:99 +msgid "To subscribe to deletion/closure notifications, eBay needs a few details:" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Button to send test notification" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:101 +msgid "An *email address* to send notifications to if the endpoint is unreachable." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:107 -msgid "Using the updated synchronisation method" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:102 +msgid "The *endpoint details*:" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:109 -msgid "If you have a lot of products, the eBay API can sometimes refuse some synchronization calls due to a time-based limit on the number of requests that eBay enforces." +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:104 +msgid "The URL to Odoo's account deletion notification endpoint" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 -msgid "To fix this issue, a new implementation mechanism has been developed; however this updated mechanism is disabled by default to avoid having the 2 systems running in parallel in existing installations." +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:105 +msgid "A verification token" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:116 -msgid "To switch to the new synchronization mechanism:" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Dedicated fields to enter the endpoint details" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:119 -msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:112 +msgid "The administrator can edit the last two fields once the email address field is filled out." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:120 -msgid "Archive the old synchronization actions (both are named *Ebay: update product status*)" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:115 +msgid "Verify the connectivity with the endpoint" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 -msgid "Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:117 +msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the :guilabel:`Send Test Notification` button." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:124 -msgid "Ensure that the **Next Execution Date** for both these actions are in the near future" +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:120 +msgid "The following confirmation message should be received: \"A test notification was sent successfully!\"" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 -msgid "Starting with the next execution date, the new method will be used instead of the old one." +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Button to send test notification" msgstr "" #: ../../content/applications/sales/sales/invoicing.rst:5 @@ -7618,12 +8791,6 @@ msgstr "" msgid "In order to use multiple currencies in Odoo *Sales*, the *Accounting* application **must** be installed." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 -msgid "Settings" -msgstr "" - #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:15 msgid "Once the *Accounting* app has been installed, foreign currencies can be added to the database. Navigate to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, and locate the :guilabel:`Main Currency` setting." msgstr "" @@ -8159,430 +9326,714 @@ msgstr "" msgid "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that are specific to that particular product. Here, price rules can be edited or created at any time." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 -msgid "How the extra price rules per product page appears in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the extra price rules per product page appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 +msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 +msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 +msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +msgid "After the desired pricelist is added to the row, designate a :guilabel:`Min. Quantity` for the price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 +msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 +msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 +msgid "Click away from the row to activate Odoo's auto-save capability, meaning that newly-created price rule is now ready to be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 +msgid "Proceed to add as many unique price rules per product as desired. There is no limit to how many price rules can be added per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 +msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 +msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 +msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 +msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +msgid "Price computation" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 +msgid "On this form, first choose one of the three :guilabel:`Computation` options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 +msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 +msgid ":guilabel:`Discount`: the price computation is based on a discount." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 +msgid ":guilabel:`Formula`: the price computation is based on a formula." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "The various formula computation options present in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 +msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 +msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 +msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 +msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +msgid "Rounding is applied *after* the discount and *before* the surcharge." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 +msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 +msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 +msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 +msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 +msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 +msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 +msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 +msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products.rst:5 +msgid "Manage your products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:3 +msgid "Import products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:5 +msgid "Odoo *Sales* provides a template for importing products with categories and variants, which can be opened and edited with any spreadsheet software (Microsoft Excel, OpenOffice, Google Sheets, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:8 +msgid "When this spreadsheet is filled out properly, it can be quickly uploaded to the Odoo database. When uploaded, those products are instantly added, accessible, and editable in the product catalog." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:12 +msgid "Import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:14 +msgid "In order to import products with categories and variants, the *Import Template for Products* **must** be downloaded. Once downloaded, the template can be adjusted and customized, and then uploaded back into the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:18 +msgid "To download the necessary import template, navigate to :menuselection:`Sales app --> Products --> Products`. On the :guilabel:`Products` page, click the :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:22 +msgid "From this drop-down menu, select the :guilabel:`Import records` option." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The Import records option selectable from the gear icon on the Products page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:28 +msgid "Selecting :guilabel:`Import records` reveals a separate page with a link to download the :guilabel:`Import Template for Products`. Click that link to download the template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:35 +msgid "Once the template download is complete, open the spreadsheet file to customize it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:38 +msgid "Customize product import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:40 +msgid "When the import template has been downloaded and opened, it's time to modify its contents. However, before any changes are made, there are a few elements to keep in mind during the process:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:43 +msgid "Feel free to remove any columns that aren't deemed necessary. But, it is *strongly* advised that the :guilabel:`Internal Reference` column remains." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:46 +msgid "While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in the :guilabel:`Internal Reference` column for each product can be helpful in many cases. This can even be from previous software spreadsheets to ease the transition into Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 -msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:50 +msgid "For example, when updating imported products, the same file can be imported several times without creating duplicates, thus enhancing the efficiency and simplicity of imported product management." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 -msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:52 +msgid "Do **not** change the labels of columns that are meant to be imported. Otherwise, Odoo won't recognize them, forcing the user to map them on the import screen manually." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 -msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:54 +msgid "Feel free to add new columns to the template spreadsheet, if desired. However, to be added, those fields **must** exist in Odoo. If Odoo can't match the column name with a field, it can be matched manually during the import process." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 -msgid "After the desired pricelist is added to the row, designate a :guilabel:`Min. Quantity` for the price rule." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:58 +msgid "During the import process of the completed template, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 -msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:62 +msgid "To manually match a column name with a field in Odoo, click the :guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` that needs a manual adjustment, and select the appropriate field from that drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 -msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:0 +msgid "The Odoo Field drop-down menu next to a Field Column that needs to be manually adjusted." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 -msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:71 +msgid "Import product template spreadsheet" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 -msgid "Click away from the row to activate Odoo's auto-save capability, meaning that newly-created price rule is now ready to be used." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:73 +msgid "After customizing the product template spreadsheet, return to the Odoo product import page, where the template download link is found, and click the :guilabel:`Upload File` button in the upper-left corner." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 -msgid "Proceed to add as many unique price rules per product as desired. There is no limit to how many price rules can be added per product." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The upload file button on the import products template download page in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 -msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:81 +msgid "Then, a pop-up window appears, in which the completed product template spreadsheet file should be selected and uploaded to Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 -msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:84 +msgid "After that, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 -msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The import a file page in Odoo Sales after a product template has been uploaded." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 -msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:91 +msgid "From here, the :guilabel:`File Column` can be manually assigned to an :guilabel:`Odoo Field`, if necessary." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 -msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:94 +msgid "To make sure everything is appropriate, and all the columns and fields are lined up accurately, click the :guilabel:`Test` button in the upper-left corner." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 -msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:97 +msgid "If everything is lined up and applied correctly, Odoo reveals a blue banner at the top of the page, informing the user that :guilabel:`Everything seems valid`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 -msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The everything seems valid message that appears if file columns are entered correctly." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 -msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:104 +msgid "If there are any errors, Odoo reveals a red banner at the top of the page, with instructions of where to locate the specific issues, and how to fix them." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 -msgid "Price computation" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The import error message that appears if file columns don't match an Odoo Field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 -msgid "On this form, first choose one of the three :guilabel:`Computation` options:" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:111 +msgid "Once those errors are fixed, click :guilabel:`Test` again to ensure all necessary issues have been remedied appropriately." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 -msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:114 +msgid "If additional product template spreadsheets need to be uploaded, click the :guilabel:`Load File` button, select the desired product template spreadsheet, and repeat the process." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 -msgid ":guilabel:`Discount`: the price computation is based on a discount." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:117 +msgid "When everything is ready, click the :guilabel:`Import` button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 -msgid ":guilabel:`Formula`: the price computation is based on a formula." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:119 +msgid "When clicked, Odoo instantly imports those products, and reveals the main :guilabel:`Products` page, with a pop-up message in the upper-right corner. This pop-up message informs the user how many products were successfully imported." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 -msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The pop-up window that appears after a successful product import process in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 -msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:127 +msgid "At this point, all the newly-imported products are accessible and editable via the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 -msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:131 +msgid "Import relation fields, attributes, and variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 -msgid "The various formula computation options present in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:133 +msgid "It's important to note that an Odoo object is always related to many other objects. For example, a product is linked to product categories, attributes, vendors, and things of this nature. These links/connections are known as relations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 -msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:138 +msgid "In order to import product relations, the records of the related object **must** be imported *first* from their own list menu." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 -msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:142 +msgid "Relation fields" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 -msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:144 +msgid "On product forms in Odoo, there are a number of fields that can be modified and customized at any time. These fields are found under every tab on a product form. While these fields are easily editable directly on the product form, they can also be modified via a product import." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 -msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:148 +msgid "As mentioned, relation fields of this nature can **only** be imported for products if they already exist in the database. For example, if a user attempts to import a product with a *Product Type*, it can only be one of the preconfigured product types existing in the database (e.g. *Storable Product*, *Consumable*, etc.)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 -msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:153 +msgid "To import information for a relation field on a product import template spreadsheet, add the name of the field as a column name/title on the spreadsheet. Then, on the appropriate product line, add the desired relation field option." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 -msgid "Rounding is applied *after* the discount and *before* the surcharge." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:157 +msgid "When all desired relation field information has been entered, save the spreadsheet, and import it to the database, per the process mentioned above (:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 -msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:161 +msgid "Once the spreadsheet with the newly-configured relation field information has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 -msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:164 +msgid "When the newly-changed/modified products, complete with the new relation field information, has been imported and uploaded, that new information can be found on the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 -msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:168 +msgid "Attributes and values" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 -msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:170 +msgid "Odoo also allows users to import product attributes and values that can be used for products that already exist in the database, and/or with imported products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 -msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:173 +msgid "To import attributes and values, a separate spreadsheet or CSV file dedicated to attributes and values **must** be imported and uploaded before they can be used for other products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 -msgid "Conditions" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:176 +msgid "The column names/titles of the attributes and values spreadsheet should be as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, :guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 -msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "An attributes and values spreadsheet template for imports." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 -msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:184 +msgid ":guilabel:`Attribute`: name of the attribute (e.g. `Size`)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 -msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:185 +msgid ":guilabel:`Display Type`: display type used in the product configurator. There are three display type options:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 -msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:188 +msgid ":guilabel:`Radio`: values displayed as radio buttons" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 -msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:189 +msgid ":guilabel:`Selection`: values displayed in a selection list" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 -msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:190 +msgid ":guilabel:`Color`: values denoted as a color selection" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 -msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:192 +msgid ":guilabel:`Variant Creation Mode`: how the variants are created when applied to a product. There are three variant creation mode options:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 -msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:195 +msgid ":guilabel:`Instantly`: all possible variants are created as soon as the attribute, and its values, are added to a product" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 -msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:197 +msgid ":guilabel:`Dynamically`: each variant is created **only** when its corresponding attributes and values are added to a sales order" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 -msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:199 +msgid ":guilabel:`Never`: variants are **never** created for the attribute" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 -msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:202 +msgid "The :guilabel:`Variants Creation Mode` **cannot** be changed once the attribute is used on at least one product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 -msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:205 +msgid ":guilabel:`Values/Value`: values pertaining to the corresponding attribute. If there are multiple values for the same attribute, the values need to be in individual lines on the spreadsheet." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products.rst:5 -msgid "Manage your products" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:208 +msgid "Once the desired attributes and values have been entered and saved in the spreadsheet, it's time to import and upload it into Odoo. To do that, navigate to :menuselection:`Sales app --> Configuration --> Attributes --> ⚙️ (gear) icon --> Import records --> Upload File`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:3 -msgid "How to import Products with Categories and Variants" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:212 +msgid "Once the spreadsheet with the newly-configured attributes and values has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Attributes` page. That's where those newly-added attributes and values can be found and edited, if necessary." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:5 -msgid "Import templates are provided in the **Import Tool** of the most common data to import (contacts, products, bank statements, etc.). You can open them with any spreadsheet software (Microsoft Office, OpenOffice, Google Drive, etc.)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:216 +msgid "As mentioned previously, when attributes and values have been added to the Odoo database, they can be used for existing or imported products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:11 -msgid "How to customize the file" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:220 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +msgid "Product variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:13 -msgid "Remove columns you don't need. However, we advise you to not remove the *ID* column (see why below)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:222 +msgid "When product attributes and values are configured in the database, they can be used on product import spreadsheets to add more information and detail to products being imported." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:15 -msgid "Set a unique ID to every single record by dragging down the ID sequencing." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:225 +msgid "To import products with product attributes and values, the product import template spreadsheet must be configured with specific :guilabel:`Product Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and :guilabel:`Name` columns." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:16 -msgid "Don't change the labels of columns you want to import. Otherwise, Odoo won't recognize them anymore, and you will have to map them on your own in the import screen." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:229 +msgid "There can be other columns, as well, but these columns are **required** in order to properly import products with specific variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:18 -msgid "Feel free to add new columns, but the fields need to exist in Odoo. If Odoo fails in matching the column name with a field, you can match it manually when importing by browsing a list of available fields." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "Product variants spreadsheet with product attributes and variants for import purposes." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:24 -msgid "Why an “ID” column?" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:236 +msgid ":guilabel:`Name`: product name" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:26 -msgid "The ID is a truly unique identifier for the line item. Feel free to use one from your previous software to ease the transition into Odoo." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:237 +msgid ":guilabel:`Product Attributes / Attribute`: name of attribute" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:29 -msgid "Setting an ID is not mandatory when importing, but it helps in many cases:" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:238 +msgid ":guilabel:`Product Attributes / Values`: values pertaining to the corresponding attribute" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:31 -msgid "Update imports: you can import the same file several times without creating duplicates." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:241 +msgid "To import multiple values, separate them by *just* a comma, **not** a comma followed by a space, in the product import template spreadsheet (e.g. `furniture,couch,home`)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:32 -msgid "Import relation fields (see here below)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:244 +msgid "When the desired products and product variants have been entered and saved in the spreadsheet, it's time to import and upload them into Odoo. To do that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:35 -msgid "How to import relation fields" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:248 +msgid "Once the spreadsheet with the newly-configured products and product variants has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page. That's where the newly-added products can be found." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:37 -msgid "An Odoo object is always related to many other objects (e.g., a product is linked to product categories, attributes, vendors, etc.). To import those relations, you need to import the records of the related object first from their own list menu." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:252 +msgid "To view and modify the attributes and variants on any products, select the desired product from the :guilabel:`Products` page, and click the :guilabel:`Attributes \\& Variants` tab." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:41 -msgid "You can do this using the name of the related record or its ID. The ID is expected when two records have the same name. In such a case, add \" / ID\" at the end of the column title (e.g., for product attributes: Product Attributes / Attribute / ID)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:256 +msgid ":doc:`variants`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 -msgid "Automatically get product images with Google Images" +msgid "Product images with Google Images" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 -msgid "The product images are very useful in Odoo, for example, to quickly find a product or check if you scanned the right one, but it can be a bit painful to set up especially if you have a lot of products. **Google Custom Search** allows finding images automatically for your product, based on their barcode, keeping your focus on what matters in your business." +msgid "Having appropriate product images in Odoo is useful for a number of reasons. However, if a lot of products need images, assigning them can become incredibly time-consuming." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:15 -msgid "This functionnality requires configuration both on Google and on Odoo." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:8 +msgid "Fortunately, by configuring the *Google Custom Search* API within an Odoo database, finding product images for products (based on their barcode) is extremely efficient." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:17 -msgid "With a free Google account, you can get up to 100 free images per day. If you need a higher rate, you'll have to upgrade to a billing account." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:16 +msgid "In order to utilize *Google Custom Search* within an Odoo database, both the database and the Google API must be properly configured." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:23 -msgid "Google API dashboard" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:20 +msgid "Free Google accounts allow users to select up to 100 free images per day. If a higher amount is needed, a billing upgrade is required." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:25 -msgid "Go to the `Google Cloud Platform API & Services `_ page to generate Google Custom Search API credentials. Log in with your Google account." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:26 +msgid "Google API dashboard" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 -msgid "Select or create an API project to store the credentials. Give it an explicit name (e.g. Odoo Images)." +msgid "Go to the `Google Cloud Platform API & Services `_ page to generate Google Custom Search API credentials. Then, log in with a Google account. Next, agree to their :guilabel:`Terms of Service` by checking the box, and clicking :guilabel:`Agree and Continue`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:32 +msgid "From here, select (or create) an API project to store the credentials. Start by giving it a memorable :guilabel:`Project Name`, select a :guilabel:`Location` (if any), then click :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:31 -msgid "In the credentials section, click on **Create Credentials** and select **API Keys**." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:35 +msgid "With the :guilabel:`Credentials` option selected in the left sidebar, click :guilabel:`Create Credentials`, and select :guilabel:`API key` from the drop-down menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "API & Services page on Google Cloud Platform" +msgid "API & Services page on Google Cloud Platform." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:37 -msgid "Save your **API Key**. You'll need it for the next step in Odoo!" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:42 +msgid "Doing so reveals an :guilabel:`API key created` pop-up window, containing a custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the pop-up window -- it will be used later. Once the key is copied (and saved for later use), click :guilabel:`Close` to remove the pop-up window." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:39 -msgid "Use the search bar to look for **Google Custom Search API** and select it." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The API key created pop-up window that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:50 +msgid "On this page, search for `Custom Search API`, and select it." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform" +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:45 -msgid "Enable the API." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 +msgid "From the :guilabel:`Custom Search API` page, enable the API by clicking :guilabel:`Enable`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "\"Custom Search API\" tile with Enable button highlighted on Google Cloud Platform" +msgid "\"Custom Search API\" page with Enable button highlighted on Google Cloud Platform." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:54 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:65 msgid "Google Programmable Search dashboard" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 -msgid "Go to `Google Programmable Search Engine `_ and click on **Get Started**. Log in with your Google account." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:67 +msgid "Next, go to `Google Programmable Search Engine `_, and click either of the :guilabel:`Get started` buttons. Log in with a Google account, if not already logged in." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "Google Programmable Search Engine page with the **Get Started** button on the up-right\n" -"of the page" +msgid "Google Programmable Search Engine page with the Get Started buttons." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:64 -msgid "Fill the language and the name of the search engine. Give it an explicit name (e.g. Odoo Images)." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:75 +msgid "On the :guilabel:`Create a new search engine` form, fill out the name of the search engine, along with what the engine should search, and be sure to enable :guilabel:`Image Search` and :guilabel:`SafeSearch`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:68 -msgid "Google doesn't allow to create a search engine without having entered at least one specific site to search on. You can put any website (e.g. www.google.com) for this step, we will remove it later." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Create new search engine form that appears with search engine configurations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:72 -msgid "Validate the form by clicking on **Create**. Then, go to the edition mode of the search engine that you created (either by clicking on **Control Panel** on the confirmation page or by clicking on the name of your Search Engine on the Home page)." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 +msgid "Validate the form by clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:76 -msgid "In the **basics** tab, make sure to enable **Image search**, **SafeSearch** and **Search the entire web**." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:84 +msgid "Doing so reveals a new page with the heading: :guilabel:`Your new search engine has been created`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:80 -msgid "Once **Search the entire web** is enabled, you can safely delete the site that you put at the previous step." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Your New Search Engine Has Been Created page that appears with copy code." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 -msgid "Save your **Search Engine Id**. You’ll need it for the next step in Odoo!" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:91 +msgid "From this page, click :guilabel:`Customize` to open the :menuselection:`Overview --> Basic` page. Then, copy the ID in the :guilabel:`Search engine ID` field. This ID is needed for the Odoo configuration." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88 -msgid "Odoo" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Basic overview page with search engine ID field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 +msgid "In the Odoo database, go to the :menuselection:`Settings app` and scroll to the :guilabel:`Integrations` section. From here, check the box beside :guilabel:`Google Images`. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:90 -msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, activate **Google Images** and save." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Google Images setting in the Odoo Settings app page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:93 -msgid "Go back to :menuselection:`Settings --> General Settings--> Integrations`, enter your **API Key** and **Search Engine ID** in **Google Images** settings and save again." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:112 +msgid "Next, return to the :menuselection:`Settings app`, and scroll to the :guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and :guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google Images` feature." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:99 -msgid "Automatically get your product images in Odoo" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:115 +msgid "Click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:101 -msgid "The action to automatically get your product images in Odoo appears in any Products or Product Variants list view. Here is a step-by-step guide from the Inventory app." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 +msgid "Product images in Odoo with Google Custom Search API" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 -msgid "Go to the Products menu (:menuselection:`Products --> Products` or :menuselection:`Products --> Product Variants`) from any application that uses products like Inventory or Sales." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:122 +msgid "Adding images to products in Odoo can be done on any product or product variant. This process can be completed in any Odoo application that provides access to product pages (e.g. *Sales* app, *Inventory* app, etc.)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:107 -msgid "On the list view, select the products that needs an image." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:126 +msgid "Below is a step-by-step guide detailing how to utilize the *Google Custom Search API* to assign images to products in Odoo using the Odoo *Sales* application:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:110 -msgid "Only the 10,000 first selected products or product variants will be processed." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:129 +msgid "Navigate to the :guilabel:`Products` page in the *Sales* app (:menuselection:`Sales app --> Products --> Products`). Or, navigate to the :guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales app --> Products --> Product Variants`)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:113 -msgid "Only the products or product variants with a barcode and without an image will be processed." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:132 +msgid "Select the desired product that needs an image." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:114 -msgid "If you select a product that has one or more variants from the Products view, each variant matching the previous criteria will be processed." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:135 +msgid "Only products (or product variants) that have a barcode, but **not** an image, are processed." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:117 -msgid "In the action menu, select **Get Pictures from Google Images** and validate by clicking on **Get picture**." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:137 +msgid "If a product with one or more variants is selected, each variant that matches the aforementioned criteria is processed." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 -msgid "You should see your images appearing incrementally." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:140 +msgid "Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select :guilabel:`Get Pictures from Google Images` from the menu that pops up." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:123 -msgid "Only the 10 first images are fetched immediatly. If you selected more than 10, the rest will be fetched as a background job." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Get Pictures from Google Images option from the Action drop-down menu in Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:125 -msgid "The background job process about 100 images in a minute. If you reach the quota authorized by Google (either with a free or a paid plan), the background job will put itself on hold for 24 hours and continue where it stopped the day before." +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:147 +msgid "On the pop-up window that appears, click :guilabel:`Get Pictures`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:130 -msgid "`Create, modify, or close your Google Cloud Billing account `_" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The pop-up that appears in which the user should click Get Picture in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 -msgid "Product variants" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:153 +msgid "Once clicked, the image(s) will appear incrementally." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:156 +msgid "Only the first 10 images are fetched immediately. If you selected more than 10, the rest are fetched as a background job." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:159 +msgid "The background job processes about 100 images in a minute. If the quota authorized by Google (either with a free or a paid plan) is reached, the background job puts itself on hold for 24 hours. Then, it will continue where it stopped the day before." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:164 +msgid "`Create, modify, or close your Google Cloud Billing account `_" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 @@ -9346,7 +10797,7 @@ msgid ":doc:`quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:272 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:245 msgid ":doc:`get_signature_to_validate`" msgstr "" @@ -9435,7 +10886,7 @@ msgid "Then, when the quotation is paid and confirmed, a delivery order is autom msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:273 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 msgid ":doc:`get_paid_to_validate`" msgstr "" @@ -9448,7 +10899,7 @@ msgid "The use of optional products is a marketing strategy that involves the cr msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:157 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 msgid "For instance, if a customer wants to buy a car, they have the choice to order massaging seats, as well, or ignore the offer and simply buy the car. Presenting the choice to purchase optional products enhances the customer experience." msgstr "" @@ -9469,7 +10920,7 @@ msgid "To add an optional product(s) to a quotation, click :guilabel:`Add a prod msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:178 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:179 msgid "When clicked, a drop-down menu with products from the database appear. Select the desired product from the drop-down menu to add it as an optional product to the quotation template." msgstr "" @@ -9482,7 +10933,7 @@ msgid "When a product is added, the default :guilabel:`Quantity` is `1`, but tha msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:181 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:182 msgid "To delete any line item from the :guilabel:`Optional Products` tab, click the :guilabel:`🗑️ (trash can)` icon." msgstr "" @@ -10031,114 +11482,122 @@ msgid "Start by entering a name for the template in the :guilabel:`Quotation Tem msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 -msgid "Then, in the :guilabel:`Quotation expires after` field, designate how many days the quotation template will remain valid for, or leave the field on the default `0` to keep the template valid indefinitely." +msgid "Then, in the :guilabel:`Quotation Validity` field, designate how many days the quotation template will remain valid for, or leave the field on the default `0` to keep the template valid indefinitely." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 -msgid "If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` features are activated in the :guilabel:`Settings` (:menuselection:`Sales app --> Configuration --> Settings`), those options are available in the :guilabel:`Online confirmation` field." +msgid "Next, in the :guilabel:`Confirmation Mail` field, click the blank field to reveal a drop-down menu. From the drop-down menu, select a pre-configured email template to be sent to customers upon confirmation of an order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:64 -msgid "In the :guilabel:`Online confirmation` field, check the box beside :guilabel:`Signature` to request an online signature from the customer to confirm an order. Check the box beside :guilabel:`Payment` to request an online payment from the customer to confirm an order." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 +msgid "To create a new email template directly from the :guilabel:`Confirmation Mail` field, start typing the name of the new email template in the field, and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:68 -msgid "Both options can be enabled simultaneously, in which case the customer must provide **both** a signature **and** a payment to confirm an order." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 +msgid "Selecting :guilabel:`Create` creates the email template, which can be edited later." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 -msgid "Next, in the :guilabel:`Confirmation Mail` field, click the blank field to reveal a drop-down menu. From the drop-down menu, select a pre-configured email template to be sent to customers upon confirmation of an order." +msgid "Selecting :guilabel:`Create and edit...` creates the email template, and a :guilabel:`Create Confirmation Mail` pop-up window appears, in which the email template can be customized and configured right away." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:76 -msgid "To create a new email template directly from the :guilabel:`Confirmation Mail` field, start typing the name of the new email template in the field, and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Create confirmation mail pop-up window from the quotation template form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:80 -msgid "Selecting :guilabel:`Create` creates the email template, which can be edited later. Selecting :guilabel:`Create and edit...` creates the email template, and a :guilabel:`Create Confirmation Mail` pop-up window appears, in which the email template can be customized and configured right away." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 +msgid "When all modifications are complete, click :guilabel:`Save \\& Close` to save the email template and return to the quotation form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Create confirmation mail pop-up window from the quotation template form in Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 +msgid "If working in a multi-company environment, use the :guilabel:`Company` field to designate to which company this quotation template applies." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:85 +msgid "If a journal is set in the :guilabel:`Invoicing Journal` field, all sales orders with this template will invoice in that specified journal. If no journal is set in this field, the sales journal with the lowest sequence is used." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 -msgid "When all modifications are complete, click :guilabel:`Save \\& Close` to save the email template and return to the quotation form." +msgid "If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` features are activated in the :guilabel:`Settings` (:menuselection:`Sales app --> Configuration --> Settings`), those options are available on quotation template forms." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92 -msgid "If working in a multi-company environment, use the :guilabel:`Company` field to designate to which company this quotation template applies." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 +msgid "Check the box beside :guilabel:`Online Signature` to request an online signature from the customer to confirm an order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:95 -msgid "In the :guilabel:`Recurrence` field, choose from a variety of pre-configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`) to designate how often this quotation template should occur." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 +msgid "Check the box beside :guilabel:`Online Payment` to request an online payment from the customer to confirm an order. When :guilabel:`Online Payment` is checked, a new percentage field appears, in which a specific percentage of payment can be entered." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 -msgid "The :guilabel:`Recurrence` field **only** applies to subscription plans. For more information, check out the documentation on :doc:`../../subscriptions/plans`." +msgid "Both options, :guilabel:`Online Signature` and :guilabel:`Online Payment` can be enabled simultaneously, in which case the customer must provide **both** a signature **and** a payment to confirm an order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 -msgid "Lines tab" +msgid "In the :guilabel:`Recurring Plan` field, choose from a variety of pre-configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`, etc.) to designate how often this quotation template should occur." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:106 -msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking :guilabel:`Add a section` (and dragging/dropping section headers), and further explained with discretionary information (such as warranty details, terms, etc.) by clicking :guilabel:`Add a note`." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:109 +msgid "The :guilabel:`Recurring Plan` field **only** applies to subscription plans. For more information, check out the documentation on :doc:`../../subscriptions/plans`." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Populated lines tab on a quotation template form in Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:113 +msgid "Lines tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 +msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking :guilabel:`Add a section` (and dragging/dropping section headers), and further explained with discretionary information (such as warranty details, terms, etc.) by clicking :guilabel:`Add a note`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 msgid "To add a product to a quotation template, click :guilabel:`Add a product` in the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a blank field in the :guilabel:`Product` column." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:118 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:123 msgid "When clicked, a drop-down menu with existing products in the database appear. Select the desired product from the drop-down menu to add it to the quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:122 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 msgid "If the desired product isn't readily visible, type the name of the desired product in the :guilabel:`Product` field, and the option appears in the drop-down menu. Products can also be found by clicking :guilabel:`Search More...` from the drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132 msgid "When a product is added to a quotation template, the default :guilabel:`Quantity` is `1`, but that can be edited at any time." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:130 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135 msgid "Then, drag-and-drop the product to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:133 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 msgid "To add a *section*, which serves as a header to organize the lines of a sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired name of the section can be typed. When the name has been entered, click away to secure the section name." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143 msgid "Then, drag-and-drop the section name to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:141 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146 msgid "To add a note, which would appear as a piece of text for the customer on the quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired note can be typed. When the note has been entered, click away to secure the note." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:145 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 msgid "Then, drag-and-drop the note to the desired position, via the :guilabel:`six squares` icon." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:147 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152 msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right side of the line." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:151 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 msgid "Optional Products tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:153 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158 msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:161 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 msgid "Optional products appear as a section on the bottom of sales orders and eCommerce pages. Customers can immediately add them to their online sales orders themselves, if desired." msgstr "" @@ -10146,116 +11605,80 @@ msgstr "" msgid "Optional products appearing on a typical sales order with Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:168 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:173 msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally complement the original offering as added value for the prospective buyer." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Populated optional products tab on a quotation template in Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:176 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177 msgid "Clicking :guilabel:`Add a line` reveals a blank field in the :guilabel:`Product` column." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:185 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 msgid "Optional products are **not** required to create a quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:188 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:189 msgid "Terms \\& Conditions tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:190 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:191 msgid "The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add terms and conditions to the quotation template. To add terms and conditions, simply type (or copy/paste) the desired terms and conditions in this tab." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Terms and conditions tab in a quotation template form in Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:196 +msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199 -msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" +msgid "Terms and conditions are **not** required to create a quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202 -msgid "Terms and conditions are **not** required to create a quotation template." +msgid "PDF Quote Builder tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:205 -msgid "Design quotation templates" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:204 +msgid "The :guilabel:`PDF Quote Builder` tab provides options to compose an attractive quotation, with more information and visually-pleasing elements, to highlight products and/or services." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207 -msgid "In the upper-left corner of the quotation template form, there's a :guilabel:`Design Template` button." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Design template button in the upper-left corner of quotation template form." +msgid "To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages. Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:214 -msgid "When clicked, Odoo reveals a preview of the quotation template, through the Odoo *Website* application, as it will appear on the front-end of the website to the customer." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:212 +msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:218 -msgid "This feature is **only** available if the *Website* application is installed." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:220 -msgid "Odoo uses numerous blue placeholder blocks to signify where certain elements appear, and what they contain (e.g. :guilabel:`Template Header`, :guilabel:`Product`)." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:215 +msgid "Use quotation templates" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:223 -msgid "To edit the content, appearance, and overall design of the quotation template via the *Website* application, click the :guilabel:`Edit` button in the upper-right corner." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:217 +msgid "When creating a quotation (:menuselection:`Sales app --> New`), choose a pre-configured template in the :guilabel:`Quotation Template` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Design template edit button in the upper-right corner of quotation template design." +msgid "Quotation templates field on a standard quotation form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:230 -msgid "When :guilabel:`Edit` is clicked, Odoo reveals a sidebar filled with a variety of design elements and feature-rich building blocks. These building blocks can be dragged-and-dropped anywhere on the quotation template design." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:224 +msgid "To view what the customer will see, click the :guilabel:`Preview` button at the top of the page to see how the quotation template appears on the front-end of the website through Odoo's customer portal." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Design quotation template building blocks sidebar in Odoo Website." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:238 -msgid "After a block has been dropped in the desired position, it can be customized and configured to fit any unique need, look, or style." +msgid "Customer preview of a quotation template in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:242 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:233 msgid "Quotation template design uses the same methodology and functionality with design building blocks as a typical web page design with Odoo *Website*. Be sure to check out the :doc:`../../../websites/website` documentation to learn more." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237 msgid "When all blocks and customizations are complete, click the :guilabel:`Save` button to put those configurations into place." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 -msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation template form in the back-end of the *Sales* application." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:254 -msgid "Use quotation templates" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:256 -msgid "When creating a quotation (:menuselection:`Sales app --> New`), choose a pre-configured template in the :guilabel:`Quotation Template` field." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Quotation templates field on a standard quotation form in Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:263 -msgid "To view what the customer will see, click the :guilabel:`Preview` button at the top of the page to see how the quotation template appears on the front-end of the website through Odoo's customer portal." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Customer preview of a quotation template in Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:240 +msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation form in the back-end of the *Sales* application." msgstr "" #: ../../content/applications/sales/subscriptions.rst:5 @@ -10428,25 +11851,25 @@ msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:83 #: ../../content/applications/sales/subscriptions/closing.rst:105 -#: ../../content/applications/sales/subscriptions/renewals.rst:80 +#: ../../content/applications/sales/subscriptions/renewals.rst:85 #: ../../content/applications/sales/subscriptions/reports.rst:120 -#: ../../content/applications/sales/subscriptions/upselling.rst:83 +#: ../../content/applications/sales/subscriptions/upselling.rst:103 msgid ":doc:`../subscriptions`" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:84 #: ../../content/applications/sales/subscriptions/closing.rst:106 -#: ../../content/applications/sales/subscriptions/renewals.rst:81 +#: ../../content/applications/sales/subscriptions/renewals.rst:86 #: ../../content/applications/sales/subscriptions/reports.rst:121 -#: ../../content/applications/sales/subscriptions/upselling.rst:84 +#: ../../content/applications/sales/subscriptions/upselling.rst:104 msgid ":doc:`plans`" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:85 #: ../../content/applications/sales/subscriptions/closing.rst:107 -#: ../../content/applications/sales/subscriptions/renewals.rst:82 +#: ../../content/applications/sales/subscriptions/renewals.rst:87 #: ../../content/applications/sales/subscriptions/reports.rst:122 -#: ../../content/applications/sales/subscriptions/upselling.rst:85 +#: ../../content/applications/sales/subscriptions/upselling.rst:105 msgid ":doc:`products`" msgstr "" @@ -10932,71 +12355,95 @@ msgid ":doc:`ecommerce`" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:3 -msgid "Renew a subscription" +msgid "Renew subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:5 -msgid "The key feature of a subscription business model is the recurring nature of payments. In this model, customers pay a recurring amount in exchange for access to a product or a service." +msgid "The foundation of any subscription business model is recurring payments. That's when customers reliably pay a regular amount at specific intervals, in exchange for access to a subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:9 +msgid "The renewal of a subscription is the process followed by customers when they willingly choose to continue their participation (and payment) for a subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:12 +msgid "Subscribers experience the renewal process at different intervals -- weekly, monthly, annually, etc. -- depending on the duration of the agreed-upon contract." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:14 -msgid "Each subscriber experiences this renewal process monthly, annually, or sometimes more, depending on the duration of the contract. Most subscription companies choose to automate their renewal processes but, in some cases, manual subscription renewals are still the preferred option." +#: ../../content/applications/sales/subscriptions/renewals.rst:15 +msgid "Most companies that offer subscriptions prefer to automate the renewals process for customers, but, in some cases, manual subscription renewals are still used." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:18 -msgid "With **Odoo Subscriptions**, you can have all your subscriptions in one application, suggest an automatic subscription renewal to your customers (as well as a manual one) and, finally, filter all your subscriptions and easily find those to renew (with the help of the tag *To renew*)." +msgid "With the Odoo *Subscriptions* application, a company can manage all of their subscriptions in one place. Renewals can be processed automatically or manually, include additional products or upsells per renewal order, and be filtered in batch views to quickly locate customers who need to renew their subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:23 -msgid "Renew your first subscription" +#: ../../content/applications/sales/subscriptions/renewals.rst:24 +msgid "Subscription renewals" msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:25 -msgid "Before renewing a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../subscriptions>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to renew the subscription. In the Other Info tab, underneath the To Renew section, you can activate the *To renew* option. When activated, a yellow tag automatically appears in the upper right corner of the subscription." +#: ../../content/applications/sales/subscriptions/renewals.rst:26 +msgid "In order to renew a subscription, a quotation with a subscription product **must** be confirmed, with a configured :guilabel:`Recurring Plan` selected, which turns it into a sales order." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:-1 -msgid "Renew your subscription with Odoo Subscriptions" +#: ../../content/applications/sales/subscriptions/renewals.rst:30 +msgid "Only a singular product is required." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:31 +msgid "A subscription service is still a product (albeit a digital, recurring one)" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:33 +msgid "Then, that sales order needs to be confirmed, and payment from the customer for the initial subscription has to be invoiced and registered." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:36 +msgid "When those steps are complete, an :guilabel:`In Progress` tag is applied to the sales order form, and a series of buttons appear at the top of the sales order -- including a button titled, :guilabel:`Renew`." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:38 -msgid "The *To renew* tag is automatically ticked when a payment fails. This indicator also appears on the customer portal. To visualize that, you just have to click on the *Customer preview* button. The tag *To renew* appears on the top right corner." +#: ../../content/applications/sales/subscriptions/renewals.rst:-1 +msgid "Renew button on subscription sales order with Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:0 -msgid "Customer preview of a renewal with Odoo Subscriptions" +#: ../../content/applications/sales/subscriptions/renewals.rst:44 +msgid "When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new renewal quotation, complete with a :guilabel:`Renewal Quotation` tag." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:46 -msgid "When a subscription needs to be renewed, you have the possibility to use a new button called *Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales flow allowing you to send the quotation by email to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers in order to have their confirmation and, then, *Confirm* it in **Odoo Sales**." +#: ../../content/applications/sales/subscriptions/renewals.rst:-1 +msgid "Renewal quotation in the Odoo Subscriptions application." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:53 -msgid "In the Chatter of this new quotation, it is mentioned that \"This renewal order has been created from the previous subscription\". Once confirmed by your customers, this quotation becomes a sales order and a new sale is mentioned in the upper right corner of the subscription." +#: ../../content/applications/sales/subscriptions/renewals.rst:51 +msgid "From here, a standard sales flow can occur in order to confirm the quotation. This typically begins by clicking :guilabel:`Send by Email`. This sends a copy of the quotation to the customer, by email, for them to confirm, and eventually, pay for." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:0 -msgid "Renew a quotation with Odoo Subscriptions" +#: ../../content/applications/sales/subscriptions/renewals.rst:56 +msgid "In the *Chatter* of the :guilabel:`Renewal Quotation`, it is mentioned that this subscription is the renewal of the subscription from the original sales order." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:61 -msgid "By clicking on the *Sales* button, you have a summary of your sales orders in a list view. The only difference between your two quotations is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your renewal." +#: ../../content/applications/sales/subscriptions/renewals.rst:59 +msgid "Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales order, and a :guilabel:`Sales History` smart button appears at the top of the page." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:0 -msgid "Renewal as Subscription Management form in Odoo Subscriptions" +#: ../../content/applications/sales/subscriptions/renewals.rst:-1 +msgid "Sales History smart button in the Odoo Subscriptions application." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:70 -msgid "Visualize your subscriptions to renew" +#: ../../content/applications/sales/subscriptions/renewals.rst:66 +msgid "When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page, showcasing the different sales orders attached to this subscription, along with their individual :guilabel:`Subscription Status`." msgstr "" -#: ../../content/applications/sales/subscriptions/renewals.rst:72 -msgid "Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go to your *Subscriptions dashboard* and use the filter *To renew*." +#: ../../content/applications/sales/subscriptions/renewals.rst:74 +msgid "Additionally, once the :guilabel:`Renewal Quotation` is confirmed, an :guilabel:`MRR` smart button also appears at the top of the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:-1 -msgid "List view of all subscriptions and use of the filter to renew in Odoo Subscriptions" +msgid "MRR smart button in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:81 +msgid "When clicked, Odoo reveals an :guilabel:`MRR Analysis` page, detailing the monthly recurring revenue related to this specific subscription." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:3 @@ -11132,69 +12579,118 @@ msgid "Salesperson dashboard report in Odoo Subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:3 -msgid "Upsell a subscription" +#: ../../content/applications/sales/subscriptions/upselling.rst:44 +msgid "Upsell subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:5 -msgid "Subscriptions are recurrent and go on indefinitely. As time passes by, our customers may want to modify them. We must then be able to adapt the prices or change the products’ quantities to accommodate their needs. Two situations can happen:" +msgid "Subscriptions are recurrent, and go on indefinitely. As time passes, customers may want to modify them. With that in mind, it's imperative to have the ability to adapt prices, or change quantities, to accommodate any need. That's where the opportunity to upsell a subscription can come into play." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:9 -msgid "**Loyal customers:** This kind of customers already trust you as a brand. Therefore, you are confident regarding what you offer since they keep paying for your products and services. Consequently, it is easier to sell them something additional than it would be to a new customer." +msgid "Upselling may prove beneficial to the following customer types:" msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:14 -msgid "**New customers:** For this kind of customers, you have to come with something new, something attractive. What about discounts? Typically, every subscription ends after a certain given time. Making these types of offers for new customers strengthens your relationships with them and also increases their retention." +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*Loyal Customers*" msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:27 -msgid "As previously explained, to upsell a subscription to new customers, it is recommended to offer *Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and, under the *Pricing* category, you have the possibility to grant discounts on sales order lines." +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "These are customers who already trust the company/brand, and because they have established a pattern of paying for products/services, there's more confidence behind the attempt to sell them a more expensive product/service." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:-1 -msgid "Activation of the discount option in Odoo Sales" +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*New Customers*" msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:36 -msgid "Upsell your first subscription" +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "For brand new customers unfamiliar with the company/brand, a new, attractive tactic must be employed to entice them to purchase a more expensive product/service." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:38 -msgid "Before upselling a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../subscriptions>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to upsell your subscription." +#: ../../content/applications/sales/subscriptions/upselling.rst:19 +msgid "In these instances, discounts can be useful. Typically, subscriptions end after a certain period of time." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:-1 -msgid "Upsell your subscription with Odoo Subscriptions" +#: ../../content/applications/sales/subscriptions/upselling.rst:22 +msgid "So, if these more expensive products/services are offered to new customers at a discount, it can result in a sale, while establishing a strong sense of trust between the customer and the company/brand. In turn, this can increase customer retention, as they'll grow more comfortable and trustworthy over time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:28 +msgid "Discount configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:30 +msgid "In order to have the ability to upsell a subscription to a new customer, with the aid of a discount, the *Discounts* feature **must** be activated." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:48 -msgid "By using the smart button *Upsell*, you are able to create a new quotation with new subscription products and send it to your customers for approval." +#: ../../content/applications/sales/subscriptions/upselling.rst:33 +msgid "To activate the *Discounts* feature, navigate to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Pricing` section, and tick the checkbox beside :guilabel:`Discounts`. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:-1 -msgid "Add products to your subscription via the upsell option in Odoo Subscriptions" +msgid "Activation of the discount option in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:41 +msgid "With that feature activated, the ability to grant discounts on sales order lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:46 +msgid "Before upselling a subscription, check out our documentation on how to :doc:`Create a quotation <../subscriptions>` using subscription products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:49 +msgid "When a quotation with a subscription is confirmed, it officially becomes a sales order, and a new subscription is created in the Odoo *Subscriptions* application." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:56 -msgid "When the quotation is confirmed by your customers, the products are added to the initial subscription. Quotation prices are, then, prorated to the remaining time of the current invoicing period." +#: ../../content/applications/sales/subscriptions/upselling.rst:53 +msgid "The subscription sales order **must** be invoiced *before* an upsell can occur." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:60 -msgid "Of course, before sending this new quotation to your customers, you can change the unit price, taxes, and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay* this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an additional line has been added to the subscription with the new extra service the customer wanted to purchase." +#: ../../content/applications/sales/subscriptions/upselling.rst:55 +msgid "When the subscription sales order is opened, either in the *Sales* or *Subscriptions* application, the ability to upsell that subscription is available, via the :guilabel:`Upsell` button at the top of the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:-1 -msgid "Visualize all your subscriptions updates with Odoo Subscriptions" +msgid "Upsell button for subscription sales orders with Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:63 +msgid "When the :guilabel:`Upsell` button is clicked, a new quotation form appears, with an :guilabel:`Upsell` status banner in the upper-right corner. The initial subscription product is already in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:67 +msgid "There is also a warning reminding the user that the recurring products are discounted, according to the prorated period of time, located beneath the initial subscription product in the :guilabel:`Order Lines` tab." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:72 -msgid "In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list view." +#: ../../content/applications/sales/subscriptions/upselling.rst:71 +msgid "From this new upsell quotation form, add new subscription products in the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and selecting the desired subscription product." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:-1 -msgid "List view of all sales orders created for a subscription" +msgid "Adding products to your subscription via the upsell option in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:78 +msgid "Once the desired upsell subscription product(s) have been added, it can be sent to the customer for approval by clicking the :guilabel:`Send by Email` button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:82 +msgid "When the quotation is confirmed by the customer, the upsell products are added to the initial subscription. Quotation prices are then prorated to the remaining time of the current invoicing period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:87 +msgid "Before sending the new quotation to the customer, the unit price, taxes, and even discount can be applied." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:90 +msgid "Once the customer approves, click the :guilabel:`Confirm` button on the quotation, making it a sales order. When that's clicked, a :guilabel:`Sales History` smart button appears, displaying how many sales orders are attached to this initial subscription order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:94 +msgid "When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page containing a list of the related sales orders, clearly showcasing their individual :guilabel:`Subscription Status`." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:79 -msgid "The only difference between your two sales orders is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your upselling." +#: ../../content/applications/sales/subscriptions/upselling.rst:-1 +msgid "The related sales order viewable from the Sales History smart button in Odoo Subscriptions." msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index e97bd5ebf1..5d7a7fff77 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2537,7 +2537,7 @@ msgid "Project settings" msgstr "" #: ../../content/applications/services/project/project_management.rst:58 -msgid "`Odoo Tutorials: Customize your project `_" +msgid "`Odoo Tutorials: Customize projects `_" msgstr "" #: ../../content/applications/services/project/project_management.rst:61 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index e5fed3d4b0..b7fc2e1d8f 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,6 +20,206 @@ msgstr "" msgid "Websites" msgstr "" +#: ../../content/applications/websites/blog.rst:3 +msgid "Blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:5 +msgid "**Odoo Blog** allows you to create and manage blog posts on your website to engage your audience and build a community." +msgstr "" + +#: ../../content/applications/websites/blog.rst:9 +msgid "If the Blog module is not yet installed, click :guilabel:`+New` on the website builder, select :guilabel:`Blog Post`, and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:13 +msgid "Creating a blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:15 +msgid "To create or edit a blog, go to :menuselection:`Website --> Configuration --> Blogs: Blogs`. Click :guilabel:`New`, and enter the :guilabel:`Blog Name` and the :guilabel:`Blog Subtitle`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:18 +msgid "The :guilabel:`Blog` menu item is added to your website's menu the first time you create a blog and gathers all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:22 +msgid "Adding a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:24 +msgid "Go to your website, click :guilabel:`+New` in the top-right corner, and select :guilabel:`Blog Post`. In the pop-up, **select the blog** where the post should appear, write the post's :guilabel:`Title`, and :guilabel:`Save`. You can then write the post's content and customize the page using the website builder." +msgstr "" + +#: ../../content/applications/websites/blog.rst:30 +msgid "Illustrate your articles with copyright-free images from :doc:`Unsplash `." +msgstr "" + +#: ../../content/applications/websites/blog.rst:32 +msgid "Type `/` in the text editor to format and add elements to your text." +msgstr "" + +#: ../../content/applications/websites/blog.rst:35 +msgid "Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right corner to publish your post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:39 +msgid "Using tags" +msgstr "" + +#: ../../content/applications/websites/blog.rst:41 +msgid "Tags let visitors filter all posts sharing the same tag. By default, they are displayed at the bottom of posts, but can also be displayed on the blog's main page. To do so, click :menuselection:`Edit --> Customize` and enable the :guilabel:`Sidebar`. By default, the sidebar's :guilabel:`Tags List` is enabled." +msgstr "" + +#: ../../content/applications/websites/blog.rst:46 +msgid "To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: Tags` and click :guilabel:`New`. Fill in the:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:49 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/websites/blog.rst:50 +msgid ":guilabel:`Category`: tag categories let you group tags displayed on the sidebar by theme." +msgstr "" + +#: ../../content/applications/websites/blog.rst:51 +msgid ":guilabel:`Used in`: to apply the tag to existing blog posts, click :guilabel:`Add a line`, select the posts, and click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:54 +msgid "You can add and create tags directly from posts by clicking :menuselection:`Edit --> Customize` and select the post's cover. Under :guilabel:`Tags`, click :guilabel:`Choose a record...`, and select or create a tag." +msgstr "" + +#: ../../content/applications/websites/blog.rst:-1 +msgid "Adding a tag to a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:62 +msgid "To manage tag categories, go to :menuselection:`Website --> Configuration --> Blogs: Tag Categories`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:66 +msgid "Customizing blog homepages" +msgstr "" + +#: ../../content/applications/websites/blog.rst:68 +msgid "Customize the content of blog homepages by opening a blog homepage and clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:72 +msgid "Settings apply to **all** blogs homepages." +msgstr "" + +#: ../../content/applications/websites/blog.rst:74 +msgid ":guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of the latest post on the top banner, while :guilabel:`Drop Zone for Building Blocks` removes the top banner and lets you use any building block instead." +msgstr "" + +#: ../../content/applications/websites/blog.rst:78 +msgid ":guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or :guilabel:`List`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:80 +msgid ":guilabel:`Cards`: adds a *card* effect." +msgstr "" + +#: ../../content/applications/websites/blog.rst:81 +msgid ":guilabel:`Increase Readability`: improves the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:83 +msgid ":guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` section." +msgstr "" + +#: ../../content/applications/websites/blog.rst:85 +msgid ":guilabel:`Archives`: allows visitors to select a month and filter all posts created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:87 +msgid ":guilabel:`Follow Us`: displays links to your social media networks. They can be configured using the Social Media building block somewhere on your website." +msgstr "" + +#: ../../content/applications/websites/blog.rst:89 +msgid ":guilabel:`Tags List`: displays all tags related to a blog. Visitors can select a tag to filter all related posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:92 +msgid ":guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and :guilabel:`No Cover` hides them." +msgstr "" + +#: ../../content/applications/websites/blog.rst:95 +msgid ":guilabel:`Author`: displays the posts' authors." +msgstr "" + +#: ../../content/applications/websites/blog.rst:96 +msgid ":guilabel:`Comments/Views Stats`: displays the posts' number of comments and views." +msgstr "" + +#: ../../content/applications/websites/blog.rst:97 +msgid ":guilabel:`Teaser & Tags`: displays the posts' first sentences and tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:100 +msgid "Customizing blog posts" +msgstr "" + +#: ../../content/applications/websites/blog.rst:102 +msgid "Customize posts by opening a blog post and clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:105 +msgid "Settings apply to **all** posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:107 +msgid ":guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside the cover image, and :guilabel:`Title above Cover` displays it above." +msgstr "" + +#: ../../content/applications/websites/blog.rst:110 +msgid ":guilabel:`Increase Readability`: increases the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:112 +msgid ":guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional options:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:114 +msgid ":guilabel:`Archive`: allows visitors to select a month and filter all posts created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:116 +msgid ":guilabel:`Author`: displays the post's author and creation date." +msgstr "" + +#: ../../content/applications/websites/blog.rst:117 +msgid ":guilabel:`Blog List`: displays links to all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:118 +msgid ":guilabel:`Share Links`: displays share buttons to several social networks." +msgstr "" + +#: ../../content/applications/websites/blog.rst:119 +msgid ":guilabel:`Tags`: displays the post's tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:121 +msgid ":guilabel:`Breadcrumb`: displays the path to the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:123 +msgid ":guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the bottom, and :guilabel:`Comments` enable visitors to comment on the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:126 +msgid ":guilabel:`Select To Tweet`: visitors are offered to tweet the text they select." +msgstr "" + +#: ../../content/applications/websites/blog.rst:129 +msgid "Use :ref:`Plausible ` to keep track of the traffic on your blog." +msgstr "" + #: ../../content/applications/websites/ecommerce.rst:8 msgid "eCommerce" msgstr "" @@ -3007,26 +3207,26 @@ msgid "If this channel should only be available to site visitors in specific cou msgstr "" #: ../../content/applications/websites/livechat.rst:185 -msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." +msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." msgstr "" -#: ../../content/applications/websites/livechat.rst:191 +#: ../../content/applications/websites/livechat.rst:190 msgid "Widget" msgstr "" -#: ../../content/applications/websites/livechat.rst:193 +#: ../../content/applications/websites/livechat.rst:192 msgid "The :guilabel:`Widget` tab on the live chat channel details form provides the shortcode for an embeddable website widget. This code can be added to a website to provide access to a live chat window." msgstr "" -#: ../../content/applications/websites/livechat.rst:197 +#: ../../content/applications/websites/livechat.rst:196 msgid "The live chat widget can be added to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Livechat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply." msgstr "" -#: ../../content/applications/websites/livechat.rst:201 +#: ../../content/applications/websites/livechat.rst:200 msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the code into the `` tag on the site." msgstr "" -#: ../../content/applications/websites/livechat.rst:204 +#: ../../content/applications/websites/livechat.rst:203 msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer, and once they click the link, it will open a new chat." msgstr "" @@ -3034,23 +3234,23 @@ msgstr "" msgid "View of the widget tab for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:213 +#: ../../content/applications/websites/livechat.rst:212 msgid "Participate in a conversation" msgstr "" -#: ../../content/applications/websites/livechat.rst:215 +#: ../../content/applications/websites/livechat.rst:214 msgid "As explained above, *operators* are the users who will respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." msgstr "" -#: ../../content/applications/websites/livechat.rst:220 +#: ../../content/applications/websites/livechat.rst:219 msgid "Set an online chat name" msgstr "" -#: ../../content/applications/websites/livechat.rst:222 +#: ../../content/applications/websites/livechat.rst:221 msgid "Before participating in a live chat, operators should update their *Online Chat Name*. This is the name that will be displayed to site visitors in the live chat conversation." msgstr "" -#: ../../content/applications/websites/livechat.rst:225 +#: ../../content/applications/websites/livechat.rst:224 msgid "To update the :guilabel:`Online Chat Name`, click on the user name in the upper-right corner of any page in the database. Select :guilabel:`My Profile` to open the Profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field and enter the preferred name." msgstr "" @@ -3058,11 +3258,11 @@ msgstr "" msgid "View of the My Profile option in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:234 +#: ../../content/applications/websites/livechat.rst:233 msgid "If a users :guilabel:`Online Chat Name` is not set, the name displayed will default to the :guilabel:`User Name`." msgstr "" -#: ../../content/applications/websites/livechat.rst:238 +#: ../../content/applications/websites/livechat.rst:237 msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name." msgstr "" @@ -3070,15 +3270,15 @@ msgstr "" msgid "View of user profile in Odoo, emphasizing the Online Chat name field." msgstr "" -#: ../../content/applications/websites/livechat.rst:247 +#: ../../content/applications/websites/livechat.rst:246 msgid "Join or leave a channel" msgstr "" -#: ../../content/applications/websites/livechat.rst:249 +#: ../../content/applications/websites/livechat.rst:248 msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app and click the :guilabel:`JOIN` button on the kanban card for the appropriate channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:252 +#: ../../content/applications/websites/livechat.rst:251 msgid "Any channel where the user is currently active will show a :guilabel:`LEAVE` button. Click this button to disconnect from the channel." msgstr "" @@ -3086,19 +3286,19 @@ msgstr "" msgid "View of a channel form and the option to join a channel for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:260 +#: ../../content/applications/websites/livechat.rst:259 msgid "*Operators* that do not show any activity in Odoo for more than thirty minutes will be considered disconnected, and subsequently removed from the channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:264 +#: ../../content/applications/websites/livechat.rst:263 msgid "Manage live chat requests" msgstr "" -#: ../../content/applications/websites/livechat.rst:266 +#: ../../content/applications/websites/livechat.rst:265 msgid "When an operator is active in a channel, chat windows will open in the bottom right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location." msgstr "" -#: ../../content/applications/websites/livechat.rst:271 +#: ../../content/applications/websites/livechat.rst:270 msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar." msgstr "" @@ -3106,7 +3306,7 @@ msgstr "" msgid "View of the menu bar in Odoo emphasizing the conversations icon." msgstr "" -#: ../../content/applications/websites/livechat.rst:278 +#: ../../content/applications/websites/livechat.rst:277 msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Dashboard --> Discuss`. New conversations will appear in bold under the :guilabel:`LIVECHAT` heading along the left panel." msgstr "" @@ -3114,15 +3314,15 @@ msgstr "" msgid "View of the discuss application with a message sent through live chat in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:285 +#: ../../content/applications/websites/livechat.rst:284 msgid "Click on a conversation in the left panel to select it. This will open the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." msgstr "" -#: ../../content/applications/websites/livechat.rst:289 +#: ../../content/applications/websites/livechat.rst:288 msgid ":doc:`Get Started with Discuss `" msgstr "" -#: ../../content/applications/websites/livechat.rst:290 +#: ../../content/applications/websites/livechat.rst:289 msgid ":doc:`/applications/websites/livechat/responses`" msgstr "" @@ -3819,6 +4019,94 @@ msgstr "" msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues." msgstr "" +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3 +msgid "Address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:5 +msgid "You can use the Google Places API on your website to ensure that your users' delivery addresses exist and are understood by the carrier. The Google Places API allows developers to access detailed information about places using HTTP requests. The autocompletion predicts a list of places when the user starts typing the address." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1 +msgid "Address autocomplete example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:13 +msgid "`Google Maps Platform `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:14 +msgid "`Google Developers Documentation: Google Places API `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:18 +msgid "To do so, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Address Autocomplete` in the :guilabel:`SEO` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1 +msgid "Enable address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:24 +msgid "Insert your :guilabel:`Google Places API key` in the :guilabel:`API Key` field. If you don't have one, create yours on the `Google Cloud Console `_ and follow these steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:28 +msgid "Step 1: Enable the Google Places API" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:30 +msgid "**Create a New Project:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:32 +msgid "To enable the **Google Places API**, you first need to create a project. To do so, click :guilabel:`Select a project` in the top left corner, :guilabel:`New Project`, and follow the prompts to set up your project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:34 +msgid "**Enable the Google Places API:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:36 +msgid "Go to the :guilabel:`Enabled APIs & Services` and click :guilabel:`+ ENABLE APIS AND SERVICES.` Search for :guilabel:`\"Places API\"` and select it. Click on the :guilabel:`\"Enable\"` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:39 +msgid "Google's pricing depends on the number of requests and their complexity." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:42 +msgid "Step 2: Create API Credentials" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:44 +msgid "Go to `APIs & Services --> Credentials `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:46 +msgid "**Create credentials:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:48 +msgid "To create your credentials, go to :guilabel:`Credentials`, click :guilabel:`Create Credentials`, and select :guilabel:`API key`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:50 +msgid "Restrict the API Key (Optional)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:52 +msgid "For security purposes, you can restrict the usage of your API key. You can go to the :guilabel:`API restrictions` section to specify which APIs your key can access. For the Google Places API, you can restrict it to only allow requests from specific websites or apps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:57 +msgid "Save Your API Key: Copy your API key and securely store it." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:58 +msgid "Do not share it publicly or expose it in client-side code." +msgstr "" + #: ../../content/applications/websites/website/configuration/cookies_bar.rst:3 msgid "Cookies bar" msgstr "" @@ -4117,78 +4405,6 @@ msgstr "" msgid "Other reporting data such as eCommerce dashboard data, online sales analyses and visitors can be grouped by website if necessary. Open the search panel and select :guilabel:`Group by --> Website`." msgstr "" -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:3 -msgid "Geo IP Installation (On-Premises Database)" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:6 -msgid "Installation" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:8 -msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:12 -msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:19 -msgid "Restart the server" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:22 -msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:33 -msgid ":doc:`CLI documentation `." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:36 -msgid "Test GeoIP Geolocation In Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:38 -msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:41 -msgid "Go to your website. Open the web page that you want to test ``GeoIP``." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:42 -msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:43 -msgid "Add the following piece of XML in the page :" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:49 -msgid "Save and refresh the page." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:51 -msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:53 -msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:55 -msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:57 -msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:59 -msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." -msgstr "" - #: ../../content/applications/websites/website/configuration/spam_protection.rst:3 msgid "Forms spam protection" msgstr ""